From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Unable to a new branch with VC commit
Date: Fri, 12 Mar 2021 15:21:12 +0100 [thread overview]
Message-ID: <87zgz8e9lz.fsf@gmail.com> (raw)
In-Reply-To: <83h7lglf6e.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 12 Mar 2021 14:39:05 +0200")
>>>>> On Fri, 12 Mar 2021 14:39:05 +0200, Eli Zaretskii <eliz@gnu.org> said:
>> From: Robert Pluim <rpluim@gmail.com>
>> Date: Fri, 12 Mar 2021 10:50:10 +0100
>> Cc: help-gnu-emacs@gnu.org
>>
>> Neither git nor Mercurial fall under the "On centralized version
>> control systems" clause of the 'Creating New Branches'
>> documentation.
Eli> Is there any good reason why "C-u C-x v v" won't work for a dVCS?
Eli> There's an advantage in keeping the UI consistent as much as
Eli> reasonably practical, even though the two VCS types are very
Eli> different.
I donʼt see why it shouldn't. Someone just needs to add the right
incantations to vc-git-checkin and vc-hg-checkin (and maybe
vc-bazaar-checkin), and deprecate the vc-create-tag branch-creating
usage.
>> You should be able to create a branch on both git and
>> Mercurial by doing 'C-u C-x v s', which runs 'vc-create-tag'.
Eli> vc-create-tag is a strange name for making a branch, which probably
Eli> doesn't help discoverability.
I donʼt know the original rationale: Iʼve forgotten everything I ever
learned about the equivalence of tags and branches in RCS/CVS :-)
Robert
--
next prev parent reply other threads:[~2021-03-12 14:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 20:46 Unable to a new branch with VC commit Tero Mononen
2021-03-12 9:50 ` Robert Pluim
2021-03-12 10:15 ` Tero Mononen
2021-03-12 10:46 ` Robert Pluim
2021-03-12 12:39 ` Eli Zaretskii
2021-03-12 14:21 ` Robert Pluim [this message]
2021-03-12 15:14 ` Robert Pluim
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=87zgz8e9lz.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).