Renato Cunha <renatoc@gmail.com> [Tue, 15 Jun 2010 19:49:56 -0300] rev 11358
util.h: Utility macros for handling different Python APIs.
If we are in py3k, a IS_PY3K symbol is defined. Apart from that, byte strings
use the API defined in Python 2.6+ (_?PyBytes_.*). For Python < 2.6, the bytes
API is defined accordingly for mercurial usage (shameless copy from
bytesobject.h from Python's code). Some macros were backported from 2.6, as
inspired by rPath's pycompat.h.
Martin Geisler <mg@aragost.com> [Wed, 16 Jun 2010 12:22:14 +0200] rev 11357
relink: ensure deterministic directory walk in collect
Faheem Mitha <faheem@email.unc.edu> [Wed, 16 Jun 2010 15:20:22 +0530] rev 11356
help: add "glossary" topic
Joint work with Vishakh Harikumar, Pradeepkumar Gayam, David Champion,
Mark Booth, timeless, Matt Mackall, Heinrik Stuart, Greg Ward, and
Martin Geisler.
timeless <timeless@gmail.com> [Thu, 10 Jun 2010 15:35:06 +0200] rev 11355
relink/progress: Adding progress for collecting stage
timeless <timeless@gmail.com> [Thu, 10 Jun 2010 13:09:50 +0200] rev 11354
relink/progress: Adding progress for pruning stage
Greg Ward <greg-hg@gerg.ca> [Mon, 14 Jun 2010 16:06:52 -0400] rev 11353
merge: when current branch has 1 or > 2 heads, actually abort.
Currently merge just prints abort-like messages to stderr and then
exits with a misleading status 0 (cleverly disguised as "False").
With this change it raises Abort, just like every other fatal error.
Greg Ward <greg-hg@gerg.ca> [Tue, 15 Jun 2010 16:10:32 -0400] rev 11352
tags: remove inactive debugging code.
It was left in just in case things went wrong with the tag cache in
Mercurial 1.4, so we could easily crank up the verbosity with a
one-line change. There have been no problems in 1.4 or 1.5, so it
should be safe to drop this now.
Greg Ward <greg-hg@gerg.ca> [Tue, 15 Jun 2010 15:02:54 -0400] rev 11351
tags: remove the old non-caching implementation of findglobaltags().
It was left behind just in case the tag cache blew up in Mercurial
1.4, so we could easily revert to the non-caching code. There have
been no problems with the tag cache in 1.4 or 1.5, so it should be
safe to get rid of this code now.