From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: oub@mat.ucm.es, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: RCS: (vc-next-action 1) only New Backend
Date: Mon, 21 Sep 2015 19:59:53 +0300 [thread overview]
Message-ID: <83pp1bn1x2.fsf@gnu.org> (raw)
In-Reply-To: <560034ED.7040102@yandex.ru>
> Cc: oub@mat.ucm.es, monnier@iro.umontreal.ca, emacs-devel@gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Mon, 21 Sep 2015 19:48:45 +0300
>
> On 09/21/2015 07:12 PM, Eli Zaretskii wrote:
>
> > This option in RCS and CVS allows you to put a label on the revision,
> > giving it the name of your liking. The equivalent in Git is "git tag",
> > I think. So this sequence of commands
>
> IIUC, the point of doing this (in RCS or CVS) is to adjust the revision
> names of all subsequent commits as well. That's much closer to switching
> the branch.
It can serve both purposes: switch to a branch when REVISION specifies
a branch (as in 1.2.1.1), otherwise commit as the named REVISION. But
that's another issue.
Yes, this also affects all the subsequent commits, but that cannot be
had with a dVCS.
> A tag, in Git, just adds an extra (probably better-readable) name to a
> particular commit, and that's it.
Indeed. But it comes close, and is the most you can have for this
functionality. So instead of saying we don't support it at all, why
not use tags and say we support it as best as we can?
next prev parent reply other threads:[~2015-09-21 16:59 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 15:39 RCS: (vc-next-action 1) only New Backend Uwe Brauer
2015-09-18 17:18 ` Eli Zaretskii
2015-09-18 20:46 ` Uwe Brauer
2015-09-19 7:00 ` Eli Zaretskii
2015-09-19 8:46 ` Uwe Brauer
2015-09-19 8:59 ` David Kastrup
2015-09-19 9:23 ` Eli Zaretskii
2015-09-19 9:36 ` Uwe Brauer
2015-09-19 10:34 ` Eli Zaretskii
2015-09-19 9:30 ` Eli Zaretskii
2015-09-19 10:00 ` David Kastrup
2015-09-19 10:30 ` Uwe Brauer
2015-09-19 10:40 ` Eli Zaretskii
2015-09-19 10:58 ` David Kastrup
2015-09-19 11:06 ` Eli Zaretskii
2015-09-19 12:29 ` Uwe Brauer
2015-09-19 14:11 ` Eli Zaretskii
2015-09-19 21:15 ` Uwe Brauer
2015-09-19 16:05 ` Dmitry Gutov
2015-09-19 17:35 ` Eli Zaretskii
2015-09-19 17:41 ` Dmitry Gutov
2015-09-19 17:49 ` Eli Zaretskii
2015-09-19 19:44 ` Dmitry Gutov
2015-09-19 21:14 ` Uwe Brauer
2015-09-19 22:42 ` Dmitry Gutov
2015-09-20 6:08 ` Eli Zaretskii
2015-09-20 13:10 ` Dmitry Gutov
2015-09-20 14:49 ` Eli Zaretskii
2015-09-20 16:27 ` Stefan Monnier
2015-09-20 17:10 ` Eli Zaretskii
2015-09-20 17:15 ` Eli Zaretskii
2015-09-20 19:25 ` Stefan Monnier
2015-09-20 19:40 ` Eli Zaretskii
2015-09-20 20:53 ` Dmitry Gutov
2015-09-21 6:17 ` Eli Zaretskii
2015-09-21 2:18 ` Stefan Monnier
2015-09-21 2:29 ` Dmitry Gutov
2015-09-21 6:59 ` Eli Zaretskii
2015-09-21 14:06 ` Dmitry Gutov
2015-09-21 16:12 ` Eli Zaretskii
2015-09-21 16:48 ` Dmitry Gutov
2015-09-21 16:59 ` Eli Zaretskii [this message]
2015-09-21 17:33 ` Dmitry Gutov
2015-09-21 19:21 ` Eli Zaretskii
2015-09-21 5:30 ` David Kastrup
2015-09-21 13:14 ` Stefan Monnier
2015-09-21 7:08 ` Eli Zaretskii
2015-09-20 23:54 ` Dmitry Gutov
2015-09-21 6:52 ` Eli Zaretskii
2015-09-20 6:03 ` Eli Zaretskii
2015-09-19 20:21 ` Stefan Monnier
2015-09-19 9:31 ` Uwe Brauer
2015-09-19 17:29 ` Stefan Monnier
2015-09-19 17:45 ` Eli Zaretskii
2015-09-19 20:18 ` Stefan Monnier
2015-09-20 6:06 ` Eli Zaretskii
2015-09-19 9:21 ` Eli Zaretskii
2015-09-19 9:35 ` Uwe Brauer
2015-09-19 10:34 ` Eli Zaretskii
2015-09-19 10:35 ` Uwe Brauer
2015-09-20 10:05 ` Uwe Brauer
2015-09-20 10:45 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83pp1bn1x2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).