- Jun 27, 2011
-
-
Wagner Bruna authored
-
Martin Geisler authored
This includes four i18n changesets transplanted from the default branch to the stable branch since they were made after the freeze.
-
- Jun 23, 2011
-
-
Alexander Sauta authored
-
- Jun 21, 2011
-
-
Alexander Sauta authored
-
Alexander Sauta authored
-
- Jun 20, 2011
-
-
Alexander Sauta authored
-
- Jun 27, 2011
-
-
Wagner Bruna authored
-
Wagner Bruna authored
-
Wagner Bruna authored
-
- Jun 23, 2011
-
-
Jens Bäckman authored
-
- Jun 20, 2011
-
-
Wagner Bruna authored
-
- Jun 21, 2011
-
-
Wagner Bruna authored
-
- Jun 20, 2011
-
-
Wagner Bruna authored
-
Wagner Bruna authored
-
- Jun 25, 2011
-
-
Pierre-Yves David authored
Displaying all missing featureis help people to solve the issue (choosing the right version, creation the right repo)
-
- Jun 24, 2011
-
-
Adrian Buehlmann authored
-
Idan Kamara authored
-
Idan Kamara authored
For commands that take a repo, repo.ui is passed as the ui to runcommand. This restores that behaviour when the request has a repo.
-
Idan Kamara authored
archival.tarit closes the fileobj if one is passed to it, which is undesired when reading from '-'.
-
Idan Kamara authored
-
Idan Kamara authored
-
Idan Kamara authored
-
Idan Kamara authored
-
David Golub authored
Extension setup functions were not being called when repositories were obtained using the peer function instead of the repository function.
-
kiilerix authored
-
kiilerix authored
-
kiilerix authored
- at least on Solaris
-
Idan Kamara authored
The new behavior was breaking existing tools that relied on a sequence such as this: 1) start with a dirty working copy 2) qimport some patch 3) try to qpush it 4) old behavior would fail at this point due to outstanding changes. (new behavior would only fail if the outstanding changes and the patches changes intersect) 5) innocent user qrefreshes, gets his local changes in the imported patch It's worth considering if we can move this behavior to -f in the future.
-
Matt Mackall authored
-
Adrian Buehlmann authored
and give a more precise hint for how to revert such a file I'm using the term 'revision' instead of 'changeset' in this change to be consistent with the REV we use in the synopsis.
-
Idan Kamara authored
-
Idan Kamara authored
We were trying to call close() if repo == None and req.repo != None. This can happen when running commands that don't take a repo.
-
Adrian Buehlmann authored
and explicitly warn about uncommitted changes Examples: BEFORE: $ hg par -q 7:e81a2efd53d4 $ hg revert -r 2 abort: no files or directories specified (use --all to discard all changes) AFTER: Clean working directory (revert can be easily undone, no edits to be lost): $ hg revert -r 2 abort: no files or directories specified (use --all to revert all files, or 'hg update 2' to update) Uncommitted changes (revert --all *does* discard edits and is pretty hard to undo or even impossible if --no-backup is specified): $ hg revert -r 2 abort: no files or directories specified (uncommitted changes, use --all to discard all changes, or 'hg update 2' to update)
-
Adrian Buehlmann authored
-
- Jun 21, 2011
-
-
kiilerix authored
The existing code seemed to have incorrect assumptions about how parameter lists are represented by the parser. Now the match and replace functions have been merged and simplified by using getlist().
-
- Jun 23, 2011
-
-
Peter Arrenbrecht authored
-
- Jun 22, 2011
-
-
Adrian Buehlmann authored
BEFORE: $ hg revert abort: no files or directories specified (use --all to discard all changes) AFTER: $ hg revert abort: no files or directories specified (uncommitted merge, use --all to discard all changes, or 'hg update -C .' to abort the merge)
-
Adrian Buehlmann authored
-
Idan Kamara authored
This is a guaranteed by the protocol: clients know they need to read one chunk off of the 'o' channel and treat that as the hello message. They should ignore fields they don't recognize so they stay compatible with new versions of the server in case we decide to add something.
-
- Jun 23, 2011
-
-
kiilerix authored
-