Thu, 23 Aug 2007 22:45:41 -0700 imerge: add automerge flag to attempt to batch merge all conflicts
Brendan Cully <brendan@kublai.com> [Thu, 23 Aug 2007 22:45:41 -0700] rev 5223
imerge: add automerge flag to attempt to batch merge all conflicts
Thu, 23 Aug 2007 19:52:15 -0700 Merge with crew
Brendan Cully <brendan@kublai.com> [Thu, 23 Aug 2007 19:52:15 -0700] rev 5222
Merge with crew
Thu, 23 Aug 2007 19:51:59 -0700 imerge: fix ancestor calculation
Brendan Cully <brendan@kublai.com> [Thu, 23 Aug 2007 19:51:59 -0700] rev 5221
imerge: fix ancestor calculation If wctx already has two parents, ancestor calculation is wrong. Normally merge is called before wctx gets the second parent, so we simulate this in imerge by temporarily popping the second parent before calling filemerge. Highly dirty. This patch also handles the ParseError move from cmdutil to dispatch.
Fri, 24 Aug 2007 00:56:56 +0200 merge with crew-stable
Benoit Boissinot <benoit.boissinot@ens-lyon.org> [Fri, 24 Aug 2007 00:56:56 +0200] rev 5220
merge with crew-stable
Fri, 24 Aug 2007 00:56:08 +0200 fix test-permissions output
Benoit Boissinot <benoit.boissinot@ens-lyon.org> [Fri, 24 Aug 2007 00:56:08 +0200] rev 5219
fix test-permissions output
Fri, 24 Aug 2007 00:53:16 +0200 merge with crew-stable
Benoit Boissinot <benoit.boissinot@ens-lyon.org> [Fri, 24 Aug 2007 00:53:16 +0200] rev 5218
merge with crew-stable
Fri, 24 Aug 2007 00:52:28 +0200 testcase for issue705 (fixed by 316ce5e85b3e)
Benoit Boissinot <benoit.boissinot@ens-lyon.org> [Fri, 24 Aug 2007 00:52:28 +0200] rev 5217
testcase for issue705 (fixed by 316ce5e85b3e)
Fri, 24 Aug 2007 00:39:59 +0200 merge with crew-stable
Benoit Boissinot <benoit.boissinot@ens-lyon.org> [Fri, 24 Aug 2007 00:39:59 +0200] rev 5216
merge with crew-stable
Fri, 24 Aug 2007 00:39:16 +0200 merge with -stable
Benoit Boissinot <benoit.boissinot@ens-lyon.org> [Fri, 24 Aug 2007 00:39:16 +0200] rev 5215
merge with -stable
Fri, 24 Aug 2007 00:38:08 +0200 check exec: return fallback in case of error during the check
Benoit Boissinot <benoit.boissinot@ens-lyon.org> [Fri, 24 Aug 2007 00:38:08 +0200] rev 5214
check exec: return fallback in case of error during the check If there is any error while checking if exec is supported, we can return fallback. fix issue705
Thu, 23 Aug 2007 13:59:52 -0700 mq: some improvements to header rewriting (closes #690)
Brendan Cully <brendan@kublai.com> [Thu, 23 Aug 2007 13:59:52 -0700] rev 5213
mq: some improvements to header rewriting (closes #690) Tested with qrefresh -m against the mm series.
Thu, 23 Aug 2007 12:24:54 -0700 Merge with crew-stable
Brendan Cully <brendan@kublai.com> [Thu, 23 Aug 2007 12:24:54 -0700] rev 5212
Merge with crew-stable
Thu, 23 Aug 2007 12:23:07 -0700 Do not lose previous tags when adding a tag in raw mode
Brendan Cully <brendan@kublai.com> [Thu, 23 Aug 2007 12:23:07 -0700] rev 5211
Do not lose previous tags when adding a tag in raw mode
Thu, 23 Aug 2007 01:48:29 -0300 merge: forcefully mark files that we get from the second parent as dirty
Alexis S. L. Carvalho <alexis@cecm.usp.br> [Thu, 23 Aug 2007 01:48:29 -0300] rev 5210
merge: forcefully mark files that we get from the second parent as dirty After a hg merge, we want to include in the commit all the files that we got from the second parent, so that we have the correct file-level history. To make them visible to hg commit, we try to mark them as dirty. Unfortunately, right now we can't really mark them as dirty[1] - the best we can do is to mark them as needing a full comparison of their contents, but they will still be considered clean if they happen to be identical to the version in the first parent. This changeset extends the dirstate format in a compatible way, so that we can mark a file as dirty: Right now we use a negative file size to indicate we don't have valid stat data for this entry. In practice, this size is always -1. This patch uses -2 to indicate that the entry is dirty. Older versions of hg won't choke on this dirstate, but they may happily mark the file as clean after a full comparison, destroying all of our hard work. The patch adds a dirstate.normallookup method with the semantics of the current normaldirty, and changes normaldirty to forcefully mark the entry as dirty. This should fix issue522. [1] - well, we could put them in state 'm', but that state has a different meaning.
(0) -3000 -1000 -300 -100 -14 +14 +100 tip