- Jan 20, 2014
-
-
Wagner Bruna authored
Reported by FUJIWARA Katsunori <foozy@lares.dti.ne.jp>.
-
- Jan 08, 2014
-
-
David Soria Parra authored
The German translation for "remote" as "entfernt" can be misleading in situations where remote is used as a noun. "entfernt" is not a noun and can also mean "removed". To clarify this we rename "remote" to "Gegenseite" when used as a noun.
-
- Jan 02, 2014
-
-
Matt Mackall authored
-
Matt Mackall authored
-
Matt Mackall authored
-
- Dec 30, 2013
-
-
Katsunori FUJIWARA authored
-
- Dec 21, 2013
-
-
Yuya Nishihara authored
parse() cannot be called at the same time because a parser object keeps its states. This is no problem for command-line hg client, but it would cause strange errors in multi-threaded hgweb. Creating parser object is not too expensive. original: % python -m timeit -s 'from mercurial import revset' 'revset.parse("0::tip")' 100000 loops, best of 3: 11.3 usec per loop thread-safe: % python -m timeit -s 'from mercurial import revset' 'revset.parse("0::tip")' 100000 loops, best of 3: 13.1 usec per loop
-
- Dec 04, 2013
-
-
Matt Mackall authored
-
- Dec 12, 2013
-
-
Matt Mackall authored
-
- Dec 02, 2013
-
-
Matt Mackall authored
-
Matt Mackall authored
-
Matt Mackall authored
-
Matt Mackall authored
-
- Dec 01, 2013
-
-
Wagner Bruna authored
-
Andrej Shadura authored
As tags may have embedded spaces, and "hg tags" command doesn't escape them, the output of the command doesn't make a well-formed list, so we can't just iterate over it. Instead, apply a simple regexp to transform it to a list which we actually use. Line boundary matching should be enabled.
-
Matt Mackall authored
-
- Nov 27, 2013
-
-
Katsunori FUJIWARA authored
Existing tool like "msgfmt --check" can check typical translation problems (missing "%s" in msgstr, for example), but can't check Mercurial specific ones. For example, "msgfmt --check" can't check whether the translated string given to "ui.promptchoice()" is correct or not, even though problems like below cause run-time error or unexpected behavior: - less or more choices than msgid, - choices without '&', or - choices with '&' followed by none This patch adds the tool to check Mercurial specific translation problems in *.po files.
-
Santiago Pay=C3=A0 i Miralta authored
-
Durham Goode authored
Adds a basic test for shelving/unshelving with an unknown file present. Adds a test for unshelving on top of an existing unknown file.
-
Durham Goode authored
Previously, unshelve would temporarily commit unknown files (via addremove) in an attempt to allow unshelving into unknown files. This produced unexpected results, like the file time stamp changing and a .i file being created. This change makes it no longer use addremove. It ignores unknown files completely. If an unshelve would overwrite an unknown file, the unknown file is moved to *.orig The shelve continue/abort format is changed, but it just removes stuff from the end of the file, so it can still read the old format.
-
- Nov 26, 2013
-
-
Mads Kiilerich authored
a12798938721 introduced splitstandin on all action filenames. It would however crash on 'd' actions where the filename is None. Fix that and add test coverage for that case.
-
- Nov 22, 2013
-
-
Martin Geisler authored
-
Martin Geisler authored
-
Martin Geisler authored
-
Martin Geisler authored
-
Martin Geisler authored
-
Matt Mackall authored
-
- Nov 30, 2013
-
-
Wagner Bruna authored
-
- Nov 28, 2013
-
-
Katsunori FUJIWARA authored
-
- Nov 26, 2013
-
-
Wagner Bruna authored
-
- Nov 27, 2013
-
-
Chris Jerdonek authored
Passing a non-string to parsers.parse_index2() causes Mercurial to crash instead of raising a TypeError (found on Mac OS X 10.8.5, Python 2.7.6): import mercurial.parsers as parsers parsers.parse_index2(0, 0) Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 parsers.so 0x000000010e071c59 _index_clearcaches + 73 (parsers.c:644) 1 parsers.so 0x000000010e06f2d5 index_dealloc + 21 (parsers.c:1767) 2 parsers.so 0x000000010e074e3b parse_index2 + 347 (parsers.c:1891) 3 org.python.python 0x000000010dda8b17 PyEval_EvalFrameEx + 9911 This happens because when arguments of the wrong type are passed to parsers.parse_index2(), indexType's initialization function index_init() in parsers.c leaves the indexObject instance in a state that indexType's destructor function index_dealloc() cannot handle. This patch moves enough of the indexObject initialization code inside index_init() from after the argument validation code to before it. This way, when bad arguments are passed to index_init(), the destructor doesn't crash and the existing code to raise a TypeError works. This patch also adds a test to check that a TypeError is raised.
-
- Nov 07, 2013
-
-
Sean Farley authored
Previously, this required -f because we didn't consider obsolete changesets (and their children ... or successors of those children, etc.). We now use obsolete.foreground to calculate acceptable changesets when advancing the bookmark. Test coverage has been added.
-
- Nov 20, 2013
-
-
Simon Heimberg authored
Backslashes (\) in paths were encoded to %C5 when converting from url to string. This does not look nice for windows paths. And it introduces many problems when running tests on windows.
-
- Nov 17, 2013
-
-
Mads Kiilerich authored
git-1.8.4.2 will send messages like Cloning into 'X'... done. to stderr. Mute stderr.
-
- Nov 25, 2013
-
-
Matt Mackall authored
-
Matt Mackall authored
-
- Nov 18, 2013
-
-
Siddharth Agarwal authored
Previously, we'd acquire and release the wlock several times. This meant that other hg processes could come in and change state. Instead of that, retain the wlock for the entire duration of the strip.
-
- Nov 10, 2013
-
-
Mads Kiilerich authored
-
- Nov 08, 2013
-
-
Martin Geisler authored
When trying to turn a draft changeset into a secret changeset, I was told: % hg phase -s . cannot move 1 changesets to a more permissive phase, use --force no phases changed That message struck me as being backwards -- the secret phase feels less permissive to me since it restricts the changesets from being pushed. We don't use the word "permissive" elsewhere, 'hg help phase' talks about "lower phases" and "higher phases". I therefore reformulated the error message to be cannot move 1 changesets to a higher phase, use --force That is not perfect either, but more in line with the help text. An alternative could be cannot move phase backwards for 1 changesets, use --force which fits better with the help text for --force.
-
Isaac Jurado authored
-