- Aug 01, 2010
-
-
Matt Mackall authored
-
Matt Mackall authored
-
Wagner Bruna authored
-
Wagner Bruna authored
-
- Jul 25, 2010
-
-
Jens Bäckman authored
-
- Jul 30, 2010
-
-
timeless developer authored
-
- Jul 10, 2010
-
-
Gilles Moris authored
88fc876a4833 caused that we find the index of the moving patch in self.series but look it up in self.full_series. The difference between these is that full_series also contains comment lines, and we thus moved the wrong patch. Use back self.full_series to find the moving patch, but take care of striping the patch guard markers before comparing the patch name. Test cases have been added for comments and empty lines in self.full_series, and for the case of guarded patches. Original patch contributed by Mads Kiilerich <mads@kiilerich.com>
-
- Jul 31, 2010
-
-
Nicolas Dumazet authored
-
Nicolas Dumazet authored
-
Nicolas Dumazet authored
"hg qimport tip" would throw "abort: unable to read tip" before this.
-
- Jul 30, 2010
-
-
Nicolas Dumazet authored
-
- Jul 24, 2010
-
-
Idan Kamara authored
-
- Jul 27, 2010
-
-
Benjamin Pollack authored
(simplification and test by mpm)
-
- Jul 26, 2010
-
-
Christian Ebert authored
When cloning, prevent [keyword] filename patterns configured locally in the source directory to persist during the update in the destination. a) move [keyword] retrieval (back) to reposetup b) remove the corresponding global kwtools attributes Add test cases.
-
- Jul 21, 2010
-
-
kiilerix authored
This allows the (to me, in some setups) obvious configuration: [paths] / = * or / = ** Relative paths used to work with [collections] even though it isn't documented. Perhaps it should be documented?
-
- Jul 22, 2010
-
-
Brodie Rao authored
Aliased commands that received bad arguments would raise TypeError instead of SignatureError. This only affected commands that weren't wrapped by extensions. Using util.checksignature() in cmdalias.__call__() ensures SignatureError is raised correctly.
-
- Jul 23, 2010
-
-
kiilerix authored
Previous behavior wasn't very helpful: $ hg st foo abort: No such file or directory Now we tell more about what failed: abort: error getting current working directory: No such file or directory
-
- Jul 22, 2010
-
-
Katsunori FUJIWARA authored
some shell implementation (e.g.: dash) can not handle redirection into non-ASCII UTF-8 named file correctly.
-
Martin Geisler authored
The table should always have been a list so that extensions can append their own help topics -- hgsubversion would like to do this now.
-
Matt Mackall authored
-
- Jul 12, 2010
-
-
Christian Fischer authored
-
- Jul 21, 2010
-
-
Brodie Rao authored
-
- Jul 22, 2010
-
-
Dan Drake authored
-
Nicolas Dumazet authored
-
Nicolas Dumazet authored
-
- Jul 21, 2010
-
-
Nicolas Dumazet authored
-
kiilerix authored
Subrepos with relative paths must often be cloned to locations deep in the directory structure. This allows clone over ssh (init+push) work.
-
kiilerix authored
docutils would in some situations pick up its own manpage.py instead of doc/manpage.py. Renaming to hgmanpage.py makes it less ambiguous.
-
- Jul 19, 2010
-
-
Greg Ward authored
(makes issue2135, issue2264 more obvious, but does nothing to fix either one) This seems to happen in two distinct cases: * patch.patch() claims success but changes nothing (e.g. the transplanted changeset adds an empty file that already exists) * patch.patch() makes changes, but repo.status() fails to report them Both of these seem like bugs in other parts of Mercurial, so arguably it's not transplant's job to detect the failure to commit. However: * detecting the problem as soon as possible is desirable * it prevents a more obscure crash later, in transplants.write() * there might be other lurking (or future) bugs that cause repo.commit() to do nothing Also, in the case of issue2264 (source changesets silently dropped by transplant), the only way to spot the problem currently is the crash in transplants.write(). Failure to transplant a patch should abort immediately, whether it's user error (patch does not apply) or a Mercurial bug (e.g. repo.status() failing to report changes).
-
- Jul 20, 2010
-
-
Vishakh H authored
stripping of applied mq patches leads to wrong state recorded in status file. find all mq patches that will be affected and clean up status file before strip.
-
Nicolas Dumazet authored
When addbranchrevs extends revs, it adds changeset hashes, and not node ids. Which means that we have to lookup for revisions _after_ the addbranchrevs call, instead of before.
-
- Jul 13, 2010
-
-
kiilerix authored
By renaming before reverting the content of the file we ensure that we handle and break hardlinks properly. Handling of other hardlinks to .orig is somebody elses problem.
-
- Jul 20, 2010
-
-
Greg Ward authored
This makes it consistent with dirstate.status(), which is important if there are other extensions messing with the output of status(). Those extensions can safely assume that dirstate.status() returns a tuple of lists, because its docstring says it does. But inotifystatus.dirstate() returns a list of lists, which can break those other extensions.
-
- Jul 14, 2010
-
-
Steve Losh authored
Branches can have multiple heads, so it doesn't make sense to speak of "the head of the current branch". What update really does is try to update to the *tip* of the current branch.
-
- Jul 17, 2010
-
-
Katsunori FUJIWARA authored
Some encoding and language combinations (e.g.: UTF-8 and Japanese) cause encoding characters into sequence of bytes more than column width of them. So, encoding.colwidth() should be applied instread of len() on i18n strings. In addition to it, formatting by '%*s'/'%-*s' also uses "number of bytes" to calculate space padding size, and should be fixed, too.
-
- Jul 16, 2010
-
-
Nicolas Dumazet authored
When file is a link, we want the size of the link itself, not the size of the file it points to.
-
Martin Geisler authored
-
Martin Geisler authored
-
- Jul 15, 2010
-
-
kiilerix authored
-