[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: RCS: (vc-next-action 1) only New Backend

From: Eli Zaretskii
Subject: Re: RCS: (vc-next-action 1) only New Backend
Date: Mon, 21 Sep 2015 19:59:53 +0300

> Cc: address@hidden, address@hidden, address@hidden
> From: Dmitry Gutov <address@hidden>
> 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, 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?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]