Sat, 05 Feb 2011 13:59:34 +0000 doc: Add back quotes around filenames
Javi Merino <cibervicho@gmail.com> [Sat, 05 Feb 2011 13:59:34 +0000] rev 13344
doc: Add back quotes around filenames Filenames starting with a dot (.hg and .hgignore) confuse man when creating the ps documentation with "man -t hg >hg.ps" if they are not enclosed in back quotes.
Fri, 04 Feb 2011 09:17:07 +0100 merge with stable
Martin Geisler <mg@lazybytes.net> [Fri, 04 Feb 2011 09:17:07 +0100] rev 13343
merge with stable
Wed, 02 Feb 2011 13:51:22 +0100 opener: use posixfile to hold file open when calling nlinks()
Adrian Buehlmann <adrian@cadifra.com> [Wed, 02 Feb 2011 13:51:22 +0100] rev 13342
opener: use posixfile to hold file open when calling nlinks() Mercurial's posixfile is less intrusive on Windows than Python's open
Mon, 17 Jan 2011 09:37:20 +0100 remove pointless os.path.join calls when opening files in .hg/cache
Adrian Buehlmann <adrian@cadifra.com> [Mon, 17 Jan 2011 09:37:20 +0100] rev 13341
remove pointless os.path.join calls when opening files in .hg/cache Windows deals just fine with '/' in paths and Mercurial on Windows already does file accesses elsewhere with mixed \ and / in file paths anyway. This patch also makes the static-http repo case use proper URLs of the form http://example.com/repo/.hg/cache/branchheads http://example.com/repo/.hg/cache/tags instead of the entirely pointless http://example.com/repo/.hg/cache%5Cbranchheads http://example.com/repo/.hg/cache%5tags (as introduced by 5ccdca7df211)
Thu, 03 Feb 2011 00:27:44 -0600 backout: make help more explicit about what backout does stable
Jonathan Nieder <jrnieder@gmail.com> [Thu, 03 Feb 2011 00:27:44 -0600] rev 13340
backout: make help more explicit about what backout does The help for backout explains: The backout command merges the reverse effect of the reverted changeset into the working directory. Unfortunately, that does not make it obvious to a newcomer what the backout command does. Since it performs a 3-way merge, what is the common ancestor? Will the result be automatically committed? What is this reverted changeset --- is it the rev passed with -r on the command line or its inverse? So try to clarify the description, avoiding jargon and being explicit about what happens from the user's perspective. Thanks to Gilles Moris, Steve Borho, Kevin Bullock, and timeless for help.
Fri, 04 Feb 2011 09:05:23 +0100 subrepo: fix pruning of subrepo filenames in dirstate (issue2619) stable
trbs <trbs@trbs.net> [Fri, 04 Feb 2011 09:05:23 +0100] rev 13339
subrepo: fix pruning of subrepo filenames in dirstate (issue2619)
Tue, 01 Feb 2011 17:53:50 -0600 merge with self
Matt Mackall <mpm@selenic.com> [Tue, 01 Feb 2011 17:53:50 -0600] rev 13338
merge with self
Tue, 01 Feb 2011 17:52:25 -0600 merge with stable
Matt Mackall <mpm@selenic.com> [Tue, 01 Feb 2011 17:52:25 -0600] rev 13337
merge with stable
Tue, 01 Feb 2011 17:30:13 -0600 Added signature for changeset 2b2155623ee2 stable
Matt Mackall <mpm@selenic.com> [Tue, 01 Feb 2011 17:30:13 -0600] rev 13336
Added signature for changeset 2b2155623ee2
Tue, 01 Feb 2011 17:30:09 -0600 Added tag 1.7.5 for changeset 2b2155623ee2 stable
Matt Mackall <mpm@selenic.com> [Tue, 01 Feb 2011 17:30:09 -0600] rev 13335
Added tag 1.7.5 for changeset 2b2155623ee2
(0) -10000 -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 +10000 +30000 tip