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

[Dmitry Gutov <dgutov@yandex.ru>]

On 09/21/2015 07:59 PM, Eli Zaretskii wrote:

> 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.

Why another? Isn't it the main use case for specifying revision in this 
discussion?

> Yes, this also affects all the subsequent commits, but that cannot be
> had with a dVCS.

DVCS have a 'switch to branch' operation. It's seemingly different, but 
if the workflows are similar, the operations might look the same from 
the VC standpoint.

> 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?

Using tags here would be a low-value feature, as far as I'm concerned 
(you don't add tags as often as you switch branches). 'git tag' is easy 
to do from he terminal anyway.

Further, you don't usually add the tag to the commit right away (at 
least I don't). Tags usually designate releases or milestones of some 
kind, so first you commit, then you test the result somehow, and only 
then you "bless" it with a tag.