From: Andrii Kolomoiets <andreyk.mad@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 38425@debbugs.gnu.org
Subject: bug#38425: 27.0.50; [PATCH] vc-hg-create-tag: Possibility to create a branch
Date: Sat, 30 Nov 2019 01:03:57 +0200 [thread overview]
Message-ID: <716CCD12-9976-405D-AA79-AE8945CEB152@gmail.com> (raw)
In-Reply-To: <B26732E3-DD01-487D-8231-23E742637F43@gmail.com>
On 30 Nov 2019, at 01:01, Andrii Kolomoiets <andreyk.mad@gmail.com> wrote:
>
> On 30 Nov 2019, at 00:21, Dmitry Gutov <dgutov@yandex.ru> wrote:
>>
>> On 29.11.2019 20:30, Andrii Kolomoiets wrote:
>>> On 29 Nov 2019, at 17:14, Dmitry Gutov <dgutov@yandex.ru> wrote:
>>>>
>>>> On 29.11.2019 17:03, Andrii Kolomoiets wrote:
>>>>> +*** New user option 'vc-hg-create-bookmark' controls whether a bookmark
>>>>> +or branch will be created when you invoke 'C-u C-x v s' ('vc-create-tag')
>>>>
>>>> Do some Mercurial users or projects predominantly work with branches, while others - with bookmarks?
>>> I think so. They even can be used together in one repository.
>>
>> That "even" is why I'm asking. If, on average, the user has to deal with both then the new option won't help. vc-hg might as well only one or the other in vc-create-tag, leaving the alternative to the command line.
>
> Why not? I've added option 'ask' so user can create branch or bookmark. Default value t is set for backward capability.
Sorry, backward compatibility.
next prev parent reply other threads:[~2019-11-29 23:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 15:03 bug#38425: 27.0.50; [PATCH] vc-hg-create-tag: Possibility to create a branch Andrii Kolomoiets
2019-11-29 15:14 ` Dmitry Gutov
2019-11-29 18:30 ` Andrii Kolomoiets
2019-11-29 22:21 ` Dmitry Gutov
2019-11-29 23:01 ` Andrii Kolomoiets
2019-11-29 23:03 ` Andrii Kolomoiets [this message]
2020-08-09 12:28 ` Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=716CCD12-9976-405D-AA79-AE8945CEB152@gmail.com \
--to=andreyk.mad@gmail.com \
--cc=38425@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.