- Aug 02, 2012
-
-
Matt Mackall authored
-
Matt Mackall authored
-
- Aug 01, 2012
-
-
durin42 authored
- Jul 31, 2012
-
-
Patrick Mézard authored
Displaying multiple synopsis in online help has been broken since Matt RST refactoring, around ff26712a0c50. Rebase help is apparently the only one using this trick, just drop the second synopsis and assume people will understand as with graft help.
-
- Jul 28, 2012
-
-
Idan Kamara authored
This restores the old behaviour of clearing the filecache when the repo is destroyed but combines it with also clearing it on _rollback. Before, we tried to only call it through _rollback but that ruined callers of destroyed. Doing it on both code paths covers destroyed being called from somewhere else, e.g. strip.
-
- Jul 31, 2012
-
-
kiilerix authored
The '-' in 'merge-tools' is surprising but necessary in the configuration. Let's help those who forget that and are looking for help.
-
- Aug 01, 2012
-
-
kiilerix authored
This makes the 'additional help topics' list consistent with the output from keyword search (for instance subrepo/subrepos). The sorting by longest name was introduced in 3f6a4f1de43f. There might have been a good reason for it back then, but now it seems like a better idea to place the preferred name first in the list in helptable.
-
- Jul 31, 2012
-
-
kiilerix authored
-
- Aug 01, 2012
-
-
Patrick Mézard authored
- Append an EOL - State the changeset is skipped
-
- Jul 31, 2012
-
-
Patrick Mézard authored
If patch.patch() reports patched files when applying a changeset and the following commit says nothing changed, transplant used to abort with a RuntimeError, assuming something went wrong with patching. The mismatch is patch.patch() reports patched files, not changed ones. It could be modified to report changed files but it means duplicating work from status, may be expensive in the case of binary files, and is probably not that useful at API level. For instance, if two patches are applied on the working directory, the outcome may be nothing changed while each call would have returned modified files. The caller would have to call status() itself again. This patch fixes the issue by trusting patching code: if the patch succeeded and commit reports nothing changed, then nothing changed, patch() did not "dropped changes on the floor".
-
- Jul 29, 2012
-
-
Patrick Mézard authored
- Fix off-by-one error on displayed entries count in normal mode - Fix incorrect paging when the top revision was lower than revcount - Fix revcount not overriding web.maxshortchanges everywhere
-
Patrick Mézard authored
-
Patrick Mézard authored
-
Katsunori FUJIWARA authored
"i18n.gettext()" invocation for "editcomment" itself should have little impact for whole initialization cost of histedit, because it is already invoked for initialization of the command table entry. '\n\n' has to be added to the text being edited separately from "editcomment", because leading 'line feed' characters are not exported to "hg.pot" file correctly.
-
- Aug 02, 2012
-
-
Matt Mackall authored
-
- Aug 01, 2012
-
-
Alexander Sauta authored
-
- Jul 20, 2012
-
-
Nikolaj Sjujskij authored
-
- Aug 01, 2012
-
-
Alexander Sauta authored
-
- Jul 31, 2012
-
-
Katsunori FUJIWARA authored
-
Wagner Bruna authored
With review and suggestions by Sheila Genesine.
-
- Aug 01, 2012
-
-
Patrick Mézard authored
-
- Jul 31, 2012
-
-
Thomas Arendsen Hein authored
-
Thomas Arendsen Hein authored
Using less -S will hide possibly important information when reviewing a changeset, e.g. something wrong/dangerous after the 80th column, because "less" will not give an indication that following characters are hidden.
-
Pierre-Yves David authored
In the old code, the current length was always 0 leading to markers payload never being split.
- Jul 30, 2012
-
-
wujek srujek authored
Previously, the parents / children were computed relative to the cset of the currently shown file, which was wrong and inconsistent with diff and others. With this patch, the listed csets are those that contain changes to the currently compared file, which don't necessarily have to be the direct parents and children of the changeset itself.
-
- Jul 31, 2012
-
-
wujek srujek authored
The top-level 'comparison' template was not really needed, and it also caused a traceback to be shown for inexistent files (as reported by Ross Lagerwall). Getting rid of it makes the overall templating structure simpler and causes invalid files to be handled nicely.
-
Matt Mackall authored
-
- Jul 29, 2012
-
-
Katsunori FUJIWARA authored
-
- Jul 31, 2012
-
-
kiilerix authored
-
- Jul 28, 2012
-
-
Pierre-Yves David authored
This apply to both push and pull both when client or server.
-
Pierre-Yves David authored
We don't simply abort to allow the user to run other diagnostic commands.
-
Pierre-Yves David authored
Obsolete markers wide-usage and propagation should be avoided by default until the obsolete feature is more mature. This changeset introduce the `_enable` variable and prevent the creation of obsolete marker if the feature is set to `False` (the default). More limitation comes in followup changesets.
-
- Jul 27, 2012
-
-
Pierre-Yves David authored
Obsolete markers are now exchanged in smaller pieces that fit in a http header. This changes is done to avoid 400 bad request error when exchanging obsolete puskey over http. The last key pushed is always hold by the "dump0" key to ensure an easy place to hook for people who need it.
-
- Jul 26, 2012
-
-
Pierre-Yves David authored
-
- Jul 28, 2012
-
-
Pierre-Yves David authored
Very few data are displayed now, making it hard to debug phases and obsolete related issues.
-
- Jul 30, 2012
-
-
Patrick Mézard authored
-
Patrick Mézard authored
-
Ross Lagerwall authored
Tests fixed by Patrick Mézard <patrick@mezard.eu>
-