- Jan 02, 2013
-
-
Matt Mackall authored
-
Matt Mackall authored
-
Matt Mackall authored
-
- Jan 01, 2013
-
-
durin42 authored
This test started failing for me after midnight UTC on December 31st. Fixed it by specifying a date 7 years in the future more precisely (rather than just adding 8 to the year and specifying January 1st), which allows the test to pass both now and on 2012-12-01 at the same time.
-
- Dec 30, 2012
-
-
Pierre-Yves David authored
The active bookmark were moved to the temporary commit. When the transaction were rollbacked, the bookmark were lost. We now temporarly disable the bookmark to prevent this effect.
-
- Dec 29, 2012
-
-
Pierre-Yves David authored
The temporary commit created by amend update the dirstate. If the final commit fails, we need to invalidate the change made to the dirstate, otherwise the release of the wlock will write the dirstate created after the rollbacked temporary commit. This dirstate writing logic should probably be handled in the same object than the transaction one. However such change are too big for stable.
-
- Nov 23, 2012
-
-
Nikolaj Sjujskij authored
-
- Dec 27, 2012
-
-
Alexander Sauta authored
-
- Dec 20, 2012
-
-
Matt Mackall authored
filelog has feeds in header, but not in menu bar help has header feeds pointing to tags
-
- Dec 30, 2012
-
-
Benoit Boissinot authored
In order to get the port, wrap create server instead of hgweb_mod/hgwebdir_mod.
-
- Dec 20, 2012
-
-
Matt Mackall authored
-
- Dec 23, 2012
-
-
Matt Mackall authored
-
- Dec 28, 2012
-
-
Mads Kiilerich authored
-
- Dec 13, 2012
-
-
Mads Kiilerich authored
Problem: 'hg status' with largefiles enabled would walk through all the files that .hgignore said should be ignored. That made it slow if a lot of files were .hgignored or the cache was cold. It seems like there was a reason to this, but other improvements has rendered this unnecessary. Solution: .hgignore is now only ignored when that is requested (--ignore). This is a minimal 'stable' change. There is room for other improvement.
-
Mads Kiilerich authored
Largefiles revert do for some reason have two lfdirstates and lfdirstatestatus invocations in one function. The result from the first lfdirstate check was however not written back to the lfdirstate, and some files was thus checked twice.
-
Mads Kiilerich authored
Problem: 'hg status' kept checking largefiles with an unknown state until some other command wrote the updated dirstate. Solution: Add missing lfdirstate.write().
-
- Dec 28, 2012
-
-
Mads Kiilerich authored
Problem: getremotechanges would return the 'other' repo if nothing was incoming and there thus wasn't any bundle to base the repo on. The 'other' could be a http peer which only implement the functionality available over the http protocol. Transplant could thus fail with TypeError: argument of type 'httppeer' is not iterable Solution: Return the local repo instead of the remote peer if there is no reason to place a bundlerepo on top of the local repo.
-
- Dec 24, 2012
-
-
kiilerix authored
A type mismatch caused the search for the other head to fail. The code is fragile, and instead it ended up using the 'first' bookmark head, but the ordering is undefined and it could thus randomly use the wrong bookmarkhead and fail with: $ hg up -q -C e@diverged $ hg merge abort: merging with a working directory ancestor has no effect
-
- Nov 29, 2012
-
-
Tim Henigan authored
This comment should have been removed in b74361cf7c0a, when the call to scmutil.checknewlabel was removed.
-
- Dec 15, 2012
-
-
Idan Kamara authored
-
- Dec 10, 2012
-
-
Levi Bard authored
If we pass a directory to commit whose only commitable files are largefiles, the core commit code aborts before finding the largefiles. So we do the following: For directories that only have largefiles as matches, we explicitly add the largefiles to the matchlist and remove the directory. In other cases, we leave the match list unmodified.
-
- Dec 06, 2012
-
-
Matt Mackall authored
-
- Dec 05, 2012
-
-
Matt Mackall authored
-
- Dec 04, 2012
-
-
Julien Cristau authored
Hurd seems to set ENOENT to 2 + 2**30, unlike everyone else.
-
- Dec 03, 2012
-
-
Wagner Bruna authored
-
- Nov 30, 2012
-
-
Katsunori FUJIWARA authored
-
- Dec 03, 2012
-
-
Matt Mackall authored
-
Matt Mackall authored
-
- Nov 29, 2012
-
-
Katsunori FUJIWARA authored
Color extension achieves colorization by overriding the class of "ui" object just before command execution. Before this patch, "diff()" of abstractsubrepo and classes derived from it has no "ui" argument, so "diff()" of hgsubrepo uses "self._repo.ui" to invoke "cmdutil.diffordiffstat()". For separation of configuration between repositories, revision 573bec4ab7ba changed the initialization source of "self._repo.ui" from "ui"(overridden) to "baseui"(plain) of parent repository. And this caused break of colorization. This patch adds "ui" argument to "diff()" of abstractsubrepo and classes derived from it to pass "ui" object of caller side.
-
Pierre-Yves David authored
Rebase also have a plain `--rev` option used to select the rebase set (as `--base` or `--source` would). But the content of the --rev option was intended for the remote repo and is irrelevant for the local rebase operation. We expect `hg pull --rebase` to stick with the default behavior here: hg rebase --base . --dest tip(branch(.)) The `rev` option is dropped from the option passed to rebase.
-
- Nov 28, 2012
-
-
Matt Mackall authored
-
- Nov 27, 2012
-
-
Tim Henigan authored
Starting with 361ab1e2086f, users are no longer able to update a working copy to a branch named with a "bad" character (such as ':'). Prior to v2.4, it was possible to create branch names using "bad" characters, so this breaks backwards compatibility. Mercurial must allow users to update to existing branches with bad names. However, it should continue to prevent the creation of new branches with bad names. A test was added to confirm that 'hg update' works as expected. The test uses a bundled repo that was created with an earlier version of Mercurial.
-
- Nov 28, 2012
-
-
Pierre-Yves David authored
This is not a basic command. There is no reason new user should needs to know about it. Thanks to Matt Mackall for pointing this.
-
- Nov 25, 2012
-
-
André Sintzoff authored
-
- Nov 26, 2012
-
-
Matt Mackall authored
Looks like there are instances where sys.stdout/stderr contain file handles that are invalid. We should be tolerant of this for hook I/O redirection, as our primary concern is not garbling our own output stream.
-
Matt Mackall authored
We were attempting to redirect I/O even if no hook was actually getting called. This defers redirection until we've found something to do.
-
Matt Mackall authored
The old str-based += collector performed very nicely on Linux, but turns out to be quadratically expensive on Windows, causing chunkbuffer to dominate in profiles. This list-based version has been measured to significantly improve performance with large chunks on Windows, with negligible overall overhead on Linux (though microbenchmarks show it to be about 50% slower). This may increase memory overhead where += didn't behave quadratically. If we want to gather up 1G of data to join, we temporarily have 1G in our list and 1G in our string.
-
Matt Mackall authored
This was causing clones of the hg repo to go from 12.4s to 14.7s.
-
- Nov 16, 2012
-
-
Durham Goode authored
When commiting to a repo with lots of history (>400000 changesets) checking the results of revset.py:descendants against the subset takes some time. Since the subset equals the entire changelog, the check isn't necessary. Avoiding it in that case saves 0.1 seconds off of a 1.78 second commit. A 6% gain. We use the length of the subset to determine if it is the entire repo. There is precedence for this in revset.py:stringset.
-
Durham Goode authored
When commiting to a repo with lots of history (>400000 changesets) the filteredrevs check (added with 5c89e7fa5bc2) in changelog.py takes a bit of time even if the filteredrevs set is empty. Skipping the check in that case shaves 0.36 seconds off a 2.14 second commit. A 17% gain.
-