Sat, 31 May 2014 17:26:15 -0700 status: document the content of the returned tuple in the docstring
Pierre-Yves David <pierre-yves.david@fb.com> [Sat, 31 May 2014 17:26:15 -0700] rev 21722
status: document the content of the returned tuple in the docstring The ``status`` function returns a lot of information. We document it.
Mon, 09 Jun 2014 14:11:17 -0500 resolve: fix grammar of no matching files message
Matt Mackall <mpm@selenic.com> [Mon, 09 Jun 2014 14:11:17 -0500] rev 21721
resolve: fix grammar of no matching files message
Mon, 09 Jun 2014 13:53:23 -0500 merge with stable
Matt Mackall <mpm@selenic.com> [Mon, 09 Jun 2014 13:53:23 -0500] rev 21720
merge with stable
Fri, 06 Jun 2014 00:21:46 -0500 bash_completion: add -l|--list support for shelve
Sean Farley <sean.michael.farley@gmail.com> [Fri, 06 Jun 2014 00:21:46 -0500] rev 21719
bash_completion: add -l|--list support for shelve This was overlooked previously and found via 'hg shelve -p -l <tab>' (to show the diff of the shelved commit).
Sat, 31 May 2014 21:21:06 +0900 workingctx: duplicate status list received at _poststatus hook
Yuya Nishihara <yuya@tcha.org> [Sat, 31 May 2014 21:21:06 +0900] rev 21718
workingctx: duplicate status list received at _poststatus hook basectx.status may reorder the list after workingctx._poststatus is called, so workingctx must copy it. Otherwise, wctx.deleted() would return "unknown" files, for example.
Thu, 05 Jun 2014 15:24:29 +0530 patch: replace functions in fsbackend to use vfs
Chinmay Joshi <c@chinmayjoshi.com> [Thu, 05 Jun 2014 15:24:29 +0530] rev 21717
patch: replace functions in fsbackend to use vfs Several functions in fsbackend are replaced to use vfs functions. vfs operations are applied on filename and path is joined by _join().
Thu, 05 Jun 2014 15:16:44 +0530 vfs: add unlinkpath to vfs
Chinmay Joshi <c@chinmayjoshi.com> [Thu, 05 Jun 2014 15:16:44 +0530] rev 21716
vfs: add unlinkpath to vfs This patch adds unlinkpath() function in vfs to replace util.unlinkpath().
Thu, 05 Jun 2014 22:20:32 +0900 shelve: add option combination tests for refactoring in succeeding patch
FUJIWARA Katsunori <foozy@lares.dti.ne.jp> [Thu, 05 Jun 2014 22:20:32 +0900] rev 21715
shelve: add option combination tests for refactoring in succeeding patch
Sun, 01 Jun 2014 00:08:33 +0900 qfold: allow to specify '--message/'--logfile' and '--edit' at the same time
FUJIWARA Katsunori <foozy@lares.dti.ne.jp> [Sun, 01 Jun 2014 00:08:33 +0900] rev 21714
qfold: allow to specify '--message/'--logfile' and '--edit' at the same time Before this patch, 'hg qfold' disallows to specify '--message/'--logfile' and '--edit' at the same time. 'hg qfold' has disallowed such combination since Mercurial 0.9.2, but this restriction seems not to be reasonable for recent Mercurial, because all other commands creating new changeset allow it. This patch allows 'hg qfold' to specify '--message/'--logfile' and '--edit' at the same time like other commands creating new changeset.
Sun, 01 Jun 2014 00:08:32 +0900 qrefresh: allow to specify '--message/'--logfile' and '--edit' at the same time
FUJIWARA Katsunori <foozy@lares.dti.ne.jp> [Sun, 01 Jun 2014 00:08:32 +0900] rev 21713
qrefresh: allow to specify '--message/'--logfile' and '--edit' at the same time Before this patch, 'hg qrefresh' disallows to specify '--message/'--logfile' and '--edit' at the same time. 'hg qrefresh' has disallowed such combination since Mercurial 0.9.2, but this restriction seems not to be reasonable for recent Mercurial, because all other commands creating new changeset allow it. This patch allows 'hg qrefresh' to specify '--message/'--logfile' and '--edit' at the same time like other commands creating new changeset.
Sun, 01 Jun 2014 00:08:32 +0900 backout: accept '--edit' like other commands creating new changeset
FUJIWARA Katsunori <foozy@lares.dti.ne.jp> [Sun, 01 Jun 2014 00:08:32 +0900] rev 21712
backout: accept '--edit' like other commands creating new changeset After this patch, users can invoke editor for the commit message by '--edit' option regardless of '--message'/'--logfile'.
Sun, 01 Jun 2014 00:08:32 +0900 gpg: accept '--edit' like other commands creating new changeset
FUJIWARA Katsunori <foozy@lares.dti.ne.jp> [Sun, 01 Jun 2014 00:08:32 +0900] rev 21711
gpg: accept '--edit' like other commands creating new changeset After this patch, users can invoke editor for the commit message by '--edit' option regardless of '--message'.
Tue, 03 Jun 2014 13:49:51 -0700 memfilectx: add a size method
Sean Farley <sean.michael.farley@gmail.com> [Tue, 03 Jun 2014 13:49:51 -0700] rev 21710
memfilectx: add a size method This method is needed to have memfilectx behave like the other file contexts. We can't just inherit this method because each file context has different behavior: filectx reads from the filelog, and workingfilectx reads from the disk. Therefore, we define memfilectx to return the size of the data in memory.
Mon, 26 May 2014 19:02:11 +0200 resolve: keep wlock while resolving stable
Mads Kiilerich <madski at unity3d.com> [Mon, 26 May 2014 19:02:11 +0200] rev 21709
resolve: keep wlock while resolving This will make resolve use correct locking and thus make it more safe. Resolve is usually a long running command spending a lot of time waiting for user input on hard problems. It is thus a real world scenario to start multiple resolves at once or run other commands (such as up -C and merge) while resolve is running. Proper locking prevents that.
Thu, 05 Jun 2014 16:47:14 +0900 keyword: suppress keyword expansion while 'hg fetch' for internal merge stable
FUJIWARA Katsunori <foozy@lares.dti.ne.jp> [Thu, 05 Jun 2014 16:47:14 +0900] rev 21708
keyword: suppress keyword expansion while 'hg fetch' for internal merge Before this patch, 'hg fetch' may cause unexpected conflict, if 'hg fetch'-ed changes are located near lines in which keywords are embedded, because keywords are substituted with other strings in the working directory. This patch suppresses keyword expansion while 'hg fetch' for internal merge by adding 'fetch' to 'restricted' command list like 'merge'. This patch uses 'hg import' to safely create the new head to be merged at succeeding 'hg fetch', because: - branch of revision #10 is different from one of #11 in 'Test' repository, so just 'hg fetch -r 11' doesn't cause merging between them this means the new head should be created manually. - 'hg import' is easier and safer than 'cat <<EOF' and 'hg commit' to replay same changes including special characters like '$' safeness of 'hg import' with keyword extension is already examined in 'test-keyword.t'.
(0) -10000 -3000 -1000 -300 -100 -15 +15 +100 +300 +1000 +3000 +10000 tip