Thu, 22 Jul 2010 14:33:50 +0900 doc: remove has_key usage in hgmanpage stable
Nicolas Dumazet <nicdumz.commits@gmail.com> [Thu, 22 Jul 2010 14:33:50 +0900] rev 11643
doc: remove has_key usage in hgmanpage
Thu, 22 Jul 2010 14:30:29 +0900 gendoc: remove callable usage (check-code) stable
Nicolas Dumazet <nicdumz.commits@gmail.com> [Thu, 22 Jul 2010 14:30:29 +0900] rev 11642
gendoc: remove callable usage (check-code)
Wed, 21 Jul 2010 12:41:18 +0900 bookmarks: rewrite _bookmarks method documentation stable
Nicolas Dumazet <nicdumz.commits@gmail.com> [Wed, 21 Jul 2010 12:41:18 +0900] rev 11641
bookmarks: rewrite _bookmarks method documentation
Wed, 21 Jul 2010 19:29:57 +0200 init: create target directory recursively stable
Mads Kiilerich <mads@kiilerich.com> [Wed, 21 Jul 2010 19:29:57 +0200] rev 11640
init: create target directory recursively Subrepos with relative paths must often be cloned to locations deep in the directory structure. This allows clone over ssh (init+push) work.
Wed, 21 Jul 2010 17:51:37 +0200 doc: make sure we use our own code for generating man pages stable
Mads Kiilerich <mads@kiilerich.com> [Wed, 21 Jul 2010 17:51:37 +0200] rev 11639
doc: make sure we use our own code for generating man pages docutils would in some situations pick up its own manpage.py instead of doc/manpage.py. Renaming to hgmanpage.py makes it less ambiguous.
Sun, 18 Jul 2010 21:29:29 -0400 transplant: crash if repo.commit() finds nothing to commit stable
Greg Ward <greg-hg@gerg.ca> [Sun, 18 Jul 2010 21:29:29 -0400] rev 11638
transplant: crash if repo.commit() finds nothing to commit (makes issue2135, issue2264 more obvious, but does nothing to fix either one) This seems to happen in two distinct cases: * patch.patch() claims success but changes nothing (e.g. the transplanted changeset adds an empty file that already exists) * patch.patch() makes changes, but repo.status() fails to report them Both of these seem like bugs in other parts of Mercurial, so arguably it's not transplant's job to detect the failure to commit. However: * detecting the problem as soon as possible is desirable * it prevents a more obscure crash later, in transplants.write() * there might be other lurking (or future) bugs that cause repo.commit() to do nothing Also, in the case of issue2264 (source changesets silently dropped by transplant), the only way to spot the problem currently is the crash in transplants.write(). Failure to transplant a patch should abort immediately, whether it's user error (patch does not apply) or a Mercurial bug (e.g. repo.status() failing to report changes).
Tue, 20 Jul 2010 20:37:29 +0530 mq: cleanup status if applied mq is stripped (issue1881) stable
Vishakh H <vsh426@gmail.com> [Tue, 20 Jul 2010 20:37:29 +0530] rev 11637
mq: cleanup status if applied mq is stripped (issue1881) stripping of applied mq patches leads to wrong state recorded in status file. find all mq patches that will be affected and clean up status file before strip.
Tue, 20 Jul 2010 18:29:00 +0900 bundle: lookup revisions after addbranchrevs stable
Nicolas Dumazet <nicdumz.commits@gmail.com> [Tue, 20 Jul 2010 18:29:00 +0900] rev 11636
bundle: lookup revisions after addbranchrevs When addbranchrevs extends revs, it adds changeset hashes, and not node ids. Which means that we have to lookup for revisions _after_ the addbranchrevs call, instead of before.
(0) -10000 -3000 -1000 -300 -100 -30 -10 -8 +8 +10 +30 +100 +300 +1000 +3000 +10000 +30000 tip