- May 17, 2010
-
-
Martin Geisler authored
-
Martin Geisler authored
-
Martin Geisler authored
-
- May 16, 2010
-
-
Matt Mackall authored
-
Steve Losh authored
-
- Jan 08, 2010
-
-
Steve Borho authored
hgtk has been using these same configs since Feb. Users only have to name the tools they would like to use, ex: [extdiff] kdiff3 = meld =
-
- May 16, 2010
-
-
Yuya Nishihara authored
It makes easy to use `hg email --test` from another tool.
-
- May 03, 2010
-
-
Brodie Rao authored
With the pager as the child process instead of the parent process, the termination of the parent Mercurial process can cause the terminal to return before the pager exits. Inverting the relationship prevents that issue. Platforms without fork() will continue to use util.popen().
-
- May 16, 2010
-
-
Matt Mackall authored
-
- May 14, 2010
-
-
Ori Avtalion authored
The command arguments are "[-ac] [-r STARTREV] [REV]..."
-
Ori Avtalion authored
-
- May 04, 2010
-
-
Gilles Moris authored
In the case a file is locally tracked as copied in dirstate, and that a merge affects this file, this file should not be marked as modified in dirstate, as this will break the current copy state. Note: only affect working directory merge, not branch merge.
-
- May 15, 2010
-
-
Matt Mackall authored
bisect: clarify None return bundle: return 1 on no changes clone: return result code copy: limit errors to 0/1 commit: return 1 on no changes forget: return 1 on errors grep: return 1 if no match found remove: return 1 on errors resolve: return 1 if something fails to resolve rollback: return 1 if no rollback data
-
- May 14, 2010
-
-
Matt Mackall authored
-
Matt Mackall authored
-
- May 13, 2010
-
-
Matt Mackall authored
-
Matt Mackall authored
Move to using contexts while we're at it.
-
Matt Mackall authored
-
Matt Mackall authored
-
Matt Mackall authored
-
- May 12, 2010
-
-
Matt Mackall authored
-
- May 09, 2010
-
-
Christian Ebert authored
Provide extendable keyword.recordextensions variable, so other extensions beside hgext.record which provide the dorecord function can cooperate with hgext.keyword like so (example from crecord): def extsetup(): try: keyword = extensions.find('keyword') keyword.restricted += ' crecord qcrecord' try: # use record support in keyword.py if present keyword.recordcommands += ' crecord qcrecord' keyword.recordextensions += ' crecord' except AttributeError: pass except KeyError: pass
-
- May 12, 2010
-
-
Matt Mackall authored
-
Matt Mackall authored
-
- May 10, 2010
-
-
Gilles Moris authored
-
Gilles Moris authored
-
Gilles Moris authored
-
- May 11, 2010
-
-
Matt Mackall authored
-
Matt Mackall authored
-
Matt Mackall authored
-
- May 08, 2010
-
-
Martin Geisler authored
-
Martin Geisler authored
-
Martin Geisler authored
-
- May 11, 2010
-
-
Matt Mackall authored
-
Matt Mackall authored
This only hits if you're crazy enough to use static-http on a repository with revlogs larger than 1M. Don't do it.
-
- Dec 07, 2009
-
-
Alexander Solovyov authored
This avoids problem with unexpanded paths when it's not possible to expand it at higher level (for example, if file:~/path/ is supplied as path in schemes).
-
- May 03, 2010
-
-
Greg Ward authored
This starts at localrepository.push() and seeps down to push_addchangegroup(), push_unbundle(), prepush(), addchangegroup(), and leaks out to sshrepository.unbundle(), sshrepository.addchangegroup(), and httprepository.unbundle(). Seems to cover everything you ever wanted to know about pushing but were afraid to ask.
-
- May 01, 2010
-
-
Steve Losh authored
Currently running 'hg rename --after foo.txt bar.typo' is a silent no-op. This patch adds a warning. It also updates the copy and rename tests. No actual functionality is changed. fixes issue 1822
-
Alexander Solovyov authored
-
- May 10, 2010
-
-
Cédric Duval authored
From RFC 5322: an optional reply-to field MAY also be included, which contains the field name "Reply-To" and a comma-separated list of one or more addresses. [...] When the "Reply-To:" field is present, it indicates the address(es) to which the author of the message suggests that replies be sent. In the absence of the "Reply-To:" field, replies SHOULD by default be sent to the mailbox(es) specified in the "From:" field unless otherwise specified by the person composing the reply. Reply-To addresses may be specified either via command line with --reply-to or via the 'email' or 'patchbomb' sections of the config file.
-