From: Robert Pluim <rpluim@gmail.com>
To: Tero Mononen <tero@ooe.fi>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Unable to a new branch with VC commit
Date: Fri, 12 Mar 2021 10:50:10 +0100 [thread overview]
Message-ID: <878s6sg0q5.fsf@gmail.com> (raw)
In-Reply-To: <babe5664-6bba-c1d1-51c3-8a0d080dbd7a@ooe.fi> (Tero Mononen's message of "Thu, 11 Mar 2021 22:46:54 +0200")
>>>>> On Thu, 11 Mar 2021 22:46:54 +0200, Tero Mononen <tero@ooe.fi> said:
Tero> Dear Emacs people,
Tero> Most likely I'm doing something wrong but I don't know what.
Tero> I haven't managed to create a new Mercurial branch in
Tero> Emacs. According to manual [1] it should happen with C-u C-x
Tero> v v. It does request "New revision or backend". I give name
Tero> of the new branch, and then commit changes. Surprisingly,
Tero> commit ends up to the active branch instead of the new
Tero> one. I.e., it completely ignores my input.
Tero> I tested the same procedure also with Git and the result was
Tero> also the same.
Neither git nor Mercurial fall under the "On centralized version
control systems" clause of the 'Creating New Branches'
documentation. 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'.
Robert
--
next prev parent reply other threads:[~2021-03-12 9:50 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 [this message]
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
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=878s6sg0q5.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=tero@ooe.fi \
/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).