From: Dmitry Gutov <dgutov@yandex.ru>
To: Juri Linkov <juri@linkov.net>
Cc: 50344@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>,
50643@debbugs.gnu.org, Filipp Gunbin <fgunbin@fastmail.fm>
Subject: bug#50344: C-x v keybinding for vc-print-branch-log
Date: Mon, 20 Sep 2021 03:33:56 +0300 [thread overview]
Message-ID: <077bfc22-616e-cd67-3e84-e6917f9e2e53@yandex.ru> (raw)
In-Reply-To: <87y27sfpxz.fsf@mail.linkov.net>
On 19.09.2021 20:04, Juri Linkov wrote:
>> So far we only have one tag command, and it doubles for branches with
>> 'C-u'. The other tag-related command doesn't differentiate between branches
>> and tags.
>>
>> Would having essentially two copies of these, but with different names, be
>> a good idea?
>
> It makes sense to create a copy where the meaning of its arg
> is reversed, so by default it will operate on branches,
> and only with C-u on tags.
Yup.
But I also wonder if reading START-POINT with completion (with current
branch name as default) will make sense for creating tags in all
backends too.
>> Are there some VCS which would benefit from a more stricter differentiation
>> between the two? Hg, perhaps? I don't know how branches work there.
>
> So the question is what backends already use the arg 'branchp'?
> The search shows that vc-cvs-create-tag, vc-git-create-tag,
> vc-hg-create-tag all use this arg.
I thought of Hg in particular because there was a report or two citing
some problems with how we handle them.
And: "Mercurial offers a variety of approaches to branching, including
“named branches”, “bookmarks” (most similar to git), “anonymous
branches” and using clones."
(https://markheath.net/post/using-named-branches-in-mercurial)
That's basically all I know about it.
The introduction in
https://www.draketo.de/software/mercurial-branching-strategy, however,
sounds very similar to Git's approach.
next prev parent reply other threads:[~2021-09-20 0:33 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 18:43 bug#50344: C-x v keybinding for vc-print-branch-log Juri Linkov
2021-09-02 23:24 ` Dmitry Gutov
2021-09-03 8:15 ` Juri Linkov
2021-09-03 12:26 ` Dmitry Gutov
2021-09-03 16:18 ` Juri Linkov
2021-09-03 16:41 ` Dmitry Gutov
2021-09-04 6:33 ` Lars Ingebrigtsen
2021-09-05 16:28 ` Juri Linkov
2021-09-06 8:25 ` Lars Ingebrigtsen
2021-09-06 15:19 ` Juri Linkov
2021-09-07 15:05 ` Lars Ingebrigtsen
2021-09-08 2:58 ` Dmitry Gutov
2021-09-08 8:00 ` Lars Ingebrigtsen
2021-09-08 11:59 ` Dmitry Gutov
2021-09-09 17:39 ` Juri Linkov
2021-09-09 23:18 ` Dmitry Gutov
2021-09-10 6:46 ` Juri Linkov
2021-09-10 11:27 ` Dmitry Gutov
2021-09-10 10:32 ` Lars Ingebrigtsen
2021-09-10 11:26 ` Dmitry Gutov
2021-09-13 7:47 ` Juri Linkov
2021-10-07 7:21 ` Juri Linkov
2021-10-07 7:47 ` Eli Zaretskii
2021-10-07 7:58 ` Juri Linkov
2021-10-07 8:28 ` Eli Zaretskii
2021-10-07 11:12 ` Dmitry Gutov
2021-10-07 12:56 ` Eli Zaretskii
2021-10-07 13:06 ` Dmitry Gutov
2021-10-07 13:21 ` Eli Zaretskii
2021-10-07 13:26 ` Dmitry Gutov
2021-10-07 13:50 ` Eli Zaretskii
2021-10-07 17:36 ` Juri Linkov
2021-10-07 18:22 ` Eli Zaretskii
2021-10-07 21:49 ` Dmitry Gutov
2021-10-12 12:48 ` Filipp Gunbin
2021-10-13 1:45 ` Dmitry Gutov
2021-10-13 10:12 ` Filipp Gunbin
2021-10-13 23:37 ` Dmitry Gutov
2021-12-24 11:56 ` Philip Kaludercic
2021-12-24 12:03 ` Dmitry Gutov
2021-12-24 13:57 ` Philip Kaludercic
2021-12-24 23:45 ` Dmitry Gutov
2021-12-25 11:37 ` Philip Kaludercic
2021-12-25 12:08 ` Dmitry Gutov
2022-09-09 5:46 ` Sean Whitton
2022-09-09 6:29 ` Juri Linkov
2022-09-09 17:09 ` Lars Ingebrigtsen
2022-09-11 15:10 ` Juri Linkov
2022-09-11 15:25 ` Lars Ingebrigtsen
2022-09-12 18:07 ` Juri Linkov
2022-09-12 18:21 ` Eli Zaretskii
2022-09-12 19:13 ` Juri Linkov
2022-09-13 12:24 ` Eli Zaretskii
2022-09-12 18:57 ` Sean Whitton
2021-10-07 13:11 ` Robert Pluim
2021-10-07 13:51 ` Filipp Gunbin
2021-10-07 9:57 ` Gregory Heytings
2021-10-07 11:14 ` Dmitry Gutov
2021-10-07 11:25 ` Gregory Heytings
2021-10-07 11:35 ` Dmitry Gutov
2021-10-07 11:42 ` Gregory Heytings
2021-10-07 12:25 ` Kévin Le Gouguec
2021-10-07 12:42 ` Filipp Gunbin
2021-10-07 12:53 ` Dmitry Gutov
2021-10-07 13:11 ` Eli Zaretskii
2021-10-07 12:51 ` Eli Zaretskii
2021-10-07 17:30 ` Juri Linkov
2021-10-07 18:25 ` Eli Zaretskii
2021-09-16 11:46 ` Filipp Gunbin
2021-09-16 11:54 ` Dmitry Gutov
2021-09-17 15:15 ` Filipp Gunbin
2021-09-18 0:09 ` bug#50643: " Dmitry Gutov
2021-09-18 19:03 ` Juri Linkov
2021-09-19 0:01 ` Dmitry Gutov
2021-09-19 17:04 ` bug#50643: " Juri Linkov
2021-09-20 0:33 ` Dmitry Gutov [this message]
2021-09-20 6:49 ` Juri Linkov
2021-09-20 16:53 ` Dmitry Gutov
2021-09-20 17:31 ` Filipp Gunbin
2021-09-20 15:59 ` bug#50643: " Filipp Gunbin
2021-10-05 17:43 ` Juri Linkov
2021-10-06 0:37 ` Dmitry Gutov
2021-10-06 7:29 ` Juri Linkov
2021-10-07 0:57 ` Dmitry Gutov
2021-10-06 16:28 ` Juri Linkov
2021-10-07 0:47 ` Dmitry Gutov
2021-10-07 12:46 ` Filipp Gunbin
2021-10-07 12:55 ` Robert Pluim
2021-10-07 17:27 ` Juri Linkov
2021-09-08 2:50 ` Dmitry Gutov
2021-09-08 7:53 ` 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
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=077bfc22-616e-cd67-3e84-e6917f9e2e53@yandex.ru \
--to=dgutov@yandex.ru \
--cc=50344@debbugs.gnu.org \
--cc=50643@debbugs.gnu.org \
--cc=fgunbin@fastmail.fm \
--cc=juri@linkov.net \
--cc=larsi@gnus.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).