all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 22083@debbugs.gnu.org, oub@mat.ucm.es
Subject: bug#22083: 25.0.50; hg: adding tag enhances the rev, modeline does not reflect
Date: Fri, 04 Dec 2015 18:13:09 +0200	[thread overview]
Message-ID: <83d1umgpka.fsf@gnu.org> (raw)
In-Reply-To: <5661B569.7010700@yandex.ru>

> Cc: 22083@debbugs.gnu.org, oub@mat.ucm.es
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Fri, 4 Dec 2015 17:46:49 +0200
> 
> On 12/04/2015 05:37 PM, Eli Zaretskii wrote:
> 
> > RCS does.  SRC is just RCS in disguise, so it has them as well.
> 
> All right, then. But are they used often?

I don't know.  But with RCS, the branch and the revision are the same
thing, i.e. the revision number also encodes the branch.  So it isn't
important really.  (Same with CVS.)

> Branches are a well-used feature in Git. If the majority of users of a 
> different VCS X are not aware of branches, and don't use them, showing 
> the current branch everywhere might not be very useful.

I think all the 3 of the modern dVCSes have branches as very important
feature and the users are aware of them.

> > The revision number for a VCS that has it.  Something close, like the
> > output of "git describe", for those that don't.
> 
> 'git describe' output can be fairly long (e.g. 1.11.0-55-gegegege)

We could lose the gegegege part.

> for one, I'm not very comfortable with it (how useful exactly is it to 
> know that the branch is XY commits ahead of the latest tag?).

There's nothing else in Git that's comparable to a revision number, I
think.





  reply	other threads:[~2015-12-04 16:13 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 [this message]
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
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=83d1umgpka.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=22083@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=oub@mat.ucm.es \
    /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.