- Feb 23, 2013
-
-
Simon Heimberg authored
This lines were reported as unnecessary when running the tests on windows because the path was already printed with a slash and not a backslash.
-
Simon Heimberg authored
The test failed on windows before this patch.
-
- Feb 22, 2013
-
-
Matt Mackall authored
-
Matt Mackall authored
-
Matt Mackall authored
-
Matt Mackall authored
-
Bryan O'Sullivan authored
This saves us a couple of dict lookups in the common case, and improves the performance of the status method by 5% (measured with util.timed) in a repo with a large manifest.
-
- Feb 21, 2013
-
-
Bryan O'Sullivan authored
This improves the performance of log --patch and --stat by about 20% for moderately large manifests (e.g. mozilla-central) for the common case of no -I/-X patterns.
-
Kevin Bullock authored
Forgot to import util in mercurial.scmwindows. Error was introduced in: changeset: 18862:4c6f7f0dadab user: Kevin Bullock <kbullock@ringworld.org> date: Tue Feb 12 11:36:21 2013 -0600 summary: scmutil: split platform-specific bits into their own modules
-
- Feb 20, 2013
-
-
Bryan O'Sullivan authored
Previously, we'd run the iterator one more time than necessary, potentially doing a lot of extra work in the process.
-
Bryan O'Sullivan authored
In a large repo, running a command like "log -l1 -p" was expensive because it would always traverse 8 commits, as 8 was the initial window size. We now choose the lesser of 8 or the limit, speeding up the "log -l1 -p" case by a factor of 5.
-
Bryan O'Sullivan authored
We now wait for worker processes in a separate thread, so that we can spot failures in a timely way, wihout waiting for the progress pipe to drain. If a worker fails, we recover the pre-parallel-update behaviour of failing early by killing its peers before propagating the failure.
-
Bryan O'Sullivan authored
This is almost impossible to trigger due to the tiny time window involved.
-
Bryan O'Sullivan authored
Previously, if a worker failed, we exited with status 1. We now exit with the correct exit code (killing ourselves if necessary).
-
- Feb 19, 2013
-
-
Kevin Bullock authored
-
Kevin Bullock authored
-
- Feb 09, 2013
-
-
Na'Tosha Bard authored
After discussion, we've agreed that largefiles for newly pulled heads should not be cached by default. The use case for this is using largefiles repos with multiple remote servers (and therefore multiple remote largefiles caches), where users will be pulling from non-default locations on a regular basis. We think this use case will be significantly less common than the use case where all largefiles are stored on the same central server, so the default should be no caching. The old behavior can be obtained by passing the --cache-largefiles flag to pull.
-
- Feb 18, 2013
-
-
Matt Mackall authored
-
Matt Mackall authored
-
- Feb 17, 2013
-
-
Katsunori FUJIWARA authored
Before this patch, "hg bundle --branch foo other" fails to create bundle file, if specified "foo" branch is created newly on the local repository. "hg bundle" uses "hg.addbranchrevs(repo, other, ...)" to look branch names up, even though other outgoing-like implementation uses "hg.addbranchrevs(repo, repo, ...)". In the former invocation, "other" repository recognizes such branches as unknown, so execution is aborted. This patch uses "hg.addbranchrevs(repo, repo, ..)" in "hg bundle" to bundle revisions on such branches correctly.
-
- Feb 16, 2013
-
-
Kevin Bullock authored
-
- Feb 15, 2013
-
-
Kevin Bullock authored
We explicitly redraw before echoing the message so that it simply displays at the bottom of the window. Also simplifies the message printing by using 'echomsg' (which uses 'echohl' internally) and adds the names of the software involved for improved Googleability.
-
Pierre-Yves David authored
Adds a message displayed at each vimdiff invocation: merge conflict detected, type ":cq" to abort Vimdiff is very confusing for non-vim user (not to speak about vim user confused anyway. However it is very likely that vimdiff is picked as the mergetool of choice when using the default config: - vim is available on all UNIX system. - Its one of the rare non graphical merge tools.
-
- Feb 17, 2013
-
-
Matt Mackall authored
Pre-0.6c hgweb used text/plain for protocol responses. This meant that a web server could serve a static file and confuse a client into generating a nasty traceback. Now we insist that text/plain protocol responses not include a Content-Length, which older hgweb didn't generate but will typically be produced for static files.
-
Matt Mackall authored
When we don't get an hgweb protocol response, we dump the response to the user for diagnostic purposes (it might be a cgitb message, for instance). But if we try to clone a bundle, we don't want to show the entire bundle in the error message. Also, we don't want fetch the full bundle multiple times during fallback. So we only fetch 1k here.
-
- Feb 15, 2013
-
-
Kevin Bullock authored
We explicitly redraw before echoing the message so that it simply displays at the bottom of the window. Also simplifies the message printing by using 'echomsg' (which uses 'echohl' internally) and adds the names of the software involved for improved Googleability.
-
Pierre-Yves David authored
Adds a message displayed at each vimdiff invocation: merge conflict detected, type ":cq" to abort Vimdiff is very confusing for non-vim user (not to speak about vim user confused anyway. However it is very likely that vimdiff is picked as the mergetool of choice when using the default config: - vim is available on all UNIX system. - Its one of the rare non graphical merge tools.
-
- Feb 12, 2013
-
-
Simon Heimberg authored
As mentioned in bug 2043, --config is also not supported in an alias. So report this the same way as the other "early" options. Example with alias.broken = stat --config a.config=1 Before: $ hg broken abort: Option --config may not be abbreviated! After: $ hg broken error in definition for alias 'broken': --config may only be given on the command line
-
- Feb 14, 2013
-
-
Kevin Bullock authored
We actually -do- use the 'ui' argument to print a debug statement.
-
- Feb 13, 2013
-
-
Durham Goode authored
User 'timeless' in irc mentioned that having the blackbox be translated would result in logs that: - may be mixed language, if multiple users use the same repo - are not google searchable (since searching for english gives more results) - might not be readable by an admin if the employee is using hg in his native language And therefore we should log everything in english.
-
- Feb 12, 2013
-
-
Kevin Bullock authored
This parallels what's done for the util module, which imports either mercurial.posix or mercurial.windows as 'platform' and then slurps the appropriate functions into its own namespace.
-
Kevin Bullock authored
This cleans up the messiness of having one command call another, and makes the backout command robust against changes to the commit command.
-
Kevin Bullock authored
We create a new function commitstatus() in cmdutil that handles printing the status message(s) after a commit. This will allow other commit-like commands to use it, and in particular is step 2 towards removing backout's call to commands.commit.
-
Kevin Bullock authored
This is step 1 to remove backout's call to commands.commit. We don't use the options again anywhere below except for backout's own purposes, specifically choosing a merge tool, so we just write the commit options in directly.
-
Kevin Bullock authored
There's no way for addremove to show up in backout's opts dictionary. It was being set manually because cmdutil.commit expected it to be there (and would throw an exception if it wasn't). This was fixed waaaaaaay back in: changeset: 5829:784073457a0f user: Kirill Smelkov <kirr@mns.spb.ru> date: Thu Jan 10 12:07:18 2008 +0300 summary: cmdutil.commit: extract 'addremove' from opts carefully
-
Kevin Bullock authored
Before this change, backout would explicitly set the options it passed to commands.revert in order to fall thru most of its logic and call cmdutil.revert. This change makes it clearer what backup is trying to accomplish and makes it robust against changes to the revert command.
-
- Feb 13, 2013
-
-
Kevin Bullock authored
-
Simon Heimberg authored
-
Simon Heimberg authored
-
- Oct 15, 2012
-
-
Simon Heimberg authored
When glob lines directly match on windows, "/" (and not "\") was output in the path on the line. No glob matching is necessary in this case. The test output will look like this (when 5 tests have passed and no 4 has an unnecessary glob): ... Info, unnecessary glob: info about some/thing (glob) ..
-