From: Dmitry Gutov <dgutov@yandex.ru>
To: 22083@debbugs.gnu.org
Subject: bug#22083: 25.0.50; hg: adding tag enhances the rev, modeline does not reflect
Date: Sat, 5 Dec 2015 08:08:01 +0200 [thread overview]
Message-ID: <56627F41.3000805@yandex.ru> (raw)
In-Reply-To: <87vb8eto9d.fsf@mat.ucm.es>
On 12/04/2015 02:02 PM, Uwe Brauer wrote:
> Ok I try to explain again what I find confusing:
>
> Here is what I did
>
> Command line
> hg init
> create and add file test.tex
> change comit 3 times
>
> hg log --template '{rev} {latesttag}.{latesttagdistance} {desc} {files}\n'
> 2 null.3 Com3 test.tex
> 1 null.2 Com2 test.tex
> 0 null.1 Com1 test.tex
> hg tag -r 2 v1
> hg log --template '{rev} {latesttag}.{latesttagdistance} {desc} {files}\n'
> 3 v1.1 Added tag v1 for changeset 649afdff7ebe .hgtags
> 2 v1.0 Com3 test.tex
> 1 null.2 Com2 test.tex
> 0 null.1 Com1 test.tex
Tagging a revision adds a new revision? That looks odd.
> hg kwexpand
> in the file
>
> $Id: test.tex,v v1.0[Hg:2] 2015/12/03 15:15:15 oub Exp oub $
>
> change and commit in Emacs
>
> \rcsInfo $Id: test.tex,v v1.2[Hg:4] 2015/12/03 15:19:49 oub Exp oub $
>
> so there is now a jump from Hg2 to Hg:4 which is annoying.
I wonder what's going on there.
Is it somehow caused by how we perform the commit in Emacs? Is the
outcome different if you do the commit from the command line?
> Possible solutions:
>
> - The modeline string shows what «hg log» shows as a rev.
Do you mean to add the revision hash after the revision number?
How will that change improve the situation with jumping revision
numbers? Will it improve clarity somehow?
next prev parent reply other threads:[~2015-12-05 6:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 13:51 bug#22083: 25.0.50; hg: adding tag enhances the rev, modeline does not reflect Uwe Brauer
2015-12-04 3:09 ` Dmitry Gutov
2015-12-04 8:55 ` Eli Zaretskii
2015-12-04 11:41 ` Dmitry Gutov
2015-12-04 14:27 ` Eli Zaretskii
2015-12-04 14:43 ` Dmitry Gutov
2015-12-04 14:51 ` Eli Zaretskii
2015-12-04 15:15 ` Dmitry Gutov
2015-12-04 15:19 ` Eli Zaretskii
2015-12-04 15:21 ` Dmitry Gutov
2015-12-04 15:37 ` Eli Zaretskii
2015-12-04 15:46 ` Dmitry Gutov
2015-12-04 16:13 ` Eli Zaretskii
2015-12-04 17:54 ` Dmitry Gutov
2015-12-04 18:27 ` Eli Zaretskii
2015-12-04 12:02 ` Uwe Brauer
2015-12-05 6:08 ` Dmitry Gutov [this message]
2015-12-05 12:24 ` Andy Moreton
2015-12-05 19:01 ` Uwe Brauer
2015-12-05 19:08 ` Dmitry Gutov
2015-12-07 14:36 ` Andy Moreton
2015-12-07 22:05 ` Dmitry Gutov
2015-12-05 19:11 ` Uwe Brauer
2015-12-05 19:55 ` Dmitry Gutov
2015-12-05 21:36 ` Uwe Brauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56627F41.3000805@yandex.ru \
--to=dgutov@yandex.ru \
--cc=22083@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.