From: Juri Linkov <juri@linkov.net>
To: Sean Whitton <spwhitton@spwhitton.name>
Cc: emacs-devel@gnu.org
Subject: Re: binding for vc-print-branch-log
Date: Tue, 06 Sep 2022 11:10:11 +0300 [thread overview]
Message-ID: <86y1uwudng.fsf@mail.linkov.net> (raw)
In-Reply-To: <87o7vtzmh5.fsf@melete.silentflame.com> (Sean Whitton's message of "Mon, 05 Sep 2022 11:48:22 -0700")
> I accidentally reimplemented vc-print-branch-log because it doesn't show
> up when you type C-x v C-h. I think it's a pretty core operation with
> contemporary VCSs. Anyone mind if I go ahead and put it on C-x v B ?
Please see bug#50344.
next prev parent reply other threads:[~2022-09-06 8:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 18:48 binding for vc-print-branch-log Sean Whitton
2022-09-06 8:10 ` Juri Linkov [this message]
2022-09-06 22:51 ` Sean Whitton
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=86y1uwudng.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=emacs-devel@gnu.org \
--cc=spwhitton@spwhitton.name \
/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).