Thu, 18 Dec 2014 14:59:28 -0600 Added signature for changeset 6dad422ecc5a stable
Matt Mackall <mpm@selenic.com> [Thu, 18 Dec 2014 14:59:28 -0600] rev 23601
Added signature for changeset 6dad422ecc5a
Thu, 18 Dec 2014 14:59:23 -0600 Added tag 3.2.3 for changeset 6dad422ecc5a stable
Matt Mackall <mpm@selenic.com> [Thu, 18 Dec 2014 14:59:23 -0600] rev 23600
Added tag 3.2.3 for changeset 6dad422ecc5a
Thu, 18 Dec 2014 14:18:28 -0600 pathauditor: check for Windows shortname aliases stable 3.2.3
Matt Mackall <mpm@selenic.com> [Thu, 18 Dec 2014 14:18:28 -0600] rev 23599
pathauditor: check for Windows shortname aliases
Tue, 16 Dec 2014 13:08:17 -0500 pathauditor: check for codepoints ignored on OS X stable
Augie Fackler <raf@durin42.com> [Tue, 16 Dec 2014 13:08:17 -0500] rev 23598
pathauditor: check for codepoints ignored on OS X
Tue, 16 Dec 2014 13:07:10 -0500 darwin: omit ignorable codepoints when normcase()ing a file path stable
Augie Fackler <raf@durin42.com> [Tue, 16 Dec 2014 13:07:10 -0500] rev 23597
darwin: omit ignorable codepoints when normcase()ing a file path This lets us avoid some nasty case collision problems in OS X with invisible codepoints.
Tue, 16 Dec 2014 13:06:41 -0500 encoding: add hfsignoreclean to clean out HFS-ignored characters stable
Augie Fackler <raf@durin42.com> [Tue, 16 Dec 2014 13:06:41 -0500] rev 23596
encoding: add hfsignoreclean to clean out HFS-ignored characters According to Apple Technote 1150 (unavailable from Apple as far as I can tell, but archived in several places online), HFS+ ignores sixteen specific unicode runes when doing path normalization. We need to handle those cases, so this function lets us efficiently strip the offending characters from a UTF-8 encoded string (which is the only way it seems to matter on OS X.)
Thu, 11 Dec 2014 15:42:49 -0500 test-casefolding.t: demonstrate a bug with HFS+ ignoring some codepoints stable
Augie Fackler <raf@durin42.com> [Thu, 11 Dec 2014 15:42:49 -0500] rev 23595
test-casefolding.t: demonstrate a bug with HFS+ ignoring some codepoints
Fri, 12 Dec 2014 13:40:44 -0500 manifest: disallow setting the node id of an entry to None stable
Augie Fackler <augie@google.com> [Fri, 12 Dec 2014 13:40:44 -0500] rev 23594
manifest: disallow setting the node id of an entry to None manifest.diff() uses None as a special value to denote the absence of a file, so setting a file node to None means you then can't trust manifest.diff(). This should also make future manifest work slightly easier.
Fri, 12 Dec 2014 15:29:54 -0500 context: stop setting None for modified or added nodes stable
Augie Fackler <augie@google.com> [Fri, 12 Dec 2014 15:29:54 -0500] rev 23593
context: stop setting None for modified or added nodes Instead use a magic value, so that we can identify modified or added nodes correctly when using manifest.diff(). Thanks to Martin von Zweigbergk for catching that we have to update _buildstatus as well. That part eluded my debugging for some time.
Sat, 13 Dec 2014 13:33:48 -0500 largefiles: don't actually remove largefiles in an addremove dry run stable
Matt Harbison <matt_harbison@yahoo.com> [Sat, 13 Dec 2014 13:33:48 -0500] rev 23592
largefiles: don't actually remove largefiles in an addremove dry run The addlargefiles() method already properly handled dry runs.
(0) -10000 -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 +10000 tip