- Feb 06, 2010
-
-
Steve Losh authored
-
Dirkjan Ochtman authored
-
Dirkjan Ochtman authored
-
Dirkjan Ochtman authored
-
Dirkjan Ochtman authored
-
Dirkjan Ochtman authored
-
Dirkjan Ochtman authored
Hopefully we can remove it entirely in two releases or so.
-
Dirkjan Ochtman authored
-
David Soria Parra authored
-
- Feb 05, 2010
-
-
Dan Villiom Podlaski Christiansen authored
No functionality change. All tests pass.
-
Vsevolod Solovyov authored
-
Benoit Boissinot authored
-
Henri Wiechers authored
-
- Feb 01, 2010
-
-
Henri Wiechers authored
-
- Feb 05, 2010
-
-
Dirkjan Ochtman authored
-
Augie Fackler authored
-
Steve Borho authored
-
Steve Borho authored
repo.branchtags().keys() are in UTF-8, so the label should be converted to UTF-8 before checking for a naming conflict. Keep the original label for ui.status()
-
- Feb 02, 2010
-
-
Benoit Boissinot authored
-
Benoit Boissinot authored
-
- Feb 01, 2010
-
-
Matt Mackall authored
-
Matt Mackall authored
-
Matt Mackall authored
-
Matt Mackall authored
-
Wagner Bruna authored
-
Wagner Bruna authored
-
- Jan 31, 2010
-
-
Martin Geisler authored
-
- Jan 30, 2010
-
-
Georg Brandl authored
-
Katsunori FUJIWARA authored
-
- Jan 31, 2010
-
-
Matt Mackall authored
-
- Jan 24, 2010
-
-
Dan Villiom Podlaski Christiansen authored
This patch changes column headers in the templates that previously said `Last change' to `Last modified'. Neither code nor functionality are changed other than that. For some time now, I have been annoyed by the fact the `Last change' column didn't list the age of the youngest changeset in the repository, or at least tip. It just occurred to me that this is because the wording is slightly misleading; what the column in fact lists is when the repository was last *modified*, that is, when changesets was last added or removed from it. The word `change' can be understood as referring to the changeset itself. Using `changed' would be ever so slightly less amigous. However, the standard nomenclature in this case is `modification date' and `Last modified', which is incidentally entirely unambigous. Hence, `Last modified' is the wording used.
-
- Dec 10, 2009
-
-
Nicolas Dumazet authored
Following discussions with Gilles Morris [1], it seems that it is preferable to use several blacklist files in a blacklists/ directory. It is easier to add an unversioned file for experiments than modifying a tracked file. Also fall back to a simpler syntax, giving up ConfigParser, now that section names are not needed anymore. And allow --blacklist parameter to be a complete path, instead of only one of the filenames contained in tests/blacklists/ [1] http://www.selenic.com/pipermail/mercurial-devel/2009-December/017317.html
-
- Jan 31, 2010
-
-
Benoit Boissinot authored
-
Matt Mackall authored
The behavior of rebase both before and after the fix was actually incorrect, and this change regressed other parts of copy behavior.
-
- Jan 29, 2010
-
-
Matt Mackall authored
-
Matt Mackall authored
-
Matt Mackall authored
Thanks to Greg Ward for spotting and testing
-
Matt Mackall authored
Unscramble divergence test
-
- Jan 18, 2010
-
-
Jens Bäckman authored
The help text and output strings surrounding these commands are now available in glorious Swedish: outgoing, paths, recover, rename, resolve, revert, rollback, root, showconfig, tag, tags, tip This also syncs with 279c8a73fde1.
-