On Wed, May 19, 2010 at 3:36 PM, Tony Mechelynck wrote:
>
> But even if I patched version.c to add one more line to the output of
> ":version", for me the latest changeset would always be my latest commit
> (usually a merge, unless I recently made some new local changes), and that
> would not be relevant to you all. I can do with typing "hg tip" (or, after
> local changes, "hg log -l <number> -f" with a well-chosen <number>) to get
> (by copy-paste from xterm etc.) the latest changeset made by Bram, which
> would be the one just before my latest merge.
>
Hi Tony,
The following command lists the local changesets not
found in Bram's repository:
$ hg outgoing
I am managing some vim patches for pyclewn with the mq extension
(Mercurial queues). The following simple command outputs the latest
changeset made by Bram on which my patches are applied:
$ hg parents -r qbase
changeset: 2172:e12b9d992389
tag: qparent
parent: 2170:cf8f86128f4c
user: Bram Moolenaar <[email protected]>
date: Sun May 16 13:56:06 2010 +0200
summary: updated for version 7.2.436
Another advantage of using mq when applying patches, is that the patch
changeset id is temporary: when you apply the patch to a more recent
Bram's repository version, a new changeset id is created and the old
one is forgotten.
Xavier
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
