From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 63690@debbugs.gnu.org
Subject: bug#63690: 29.0.91; New vc commands missing on vc-menu
Date: Thu, 25 May 2023 10:50:56 +0300 [thread overview]
Message-ID: <83fs7kn927.fsf@gnu.org> (raw)
In-Reply-To: <86pm6o3o7l.fsf@mail.linkov.net> (message from Juri Linkov on Thu, 25 May 2023 09:43:58 +0300)
> From: Juri Linkov <juri@linkov.net>
> Cc: 63690@debbugs.gnu.org
> Date: Thu, 25 May 2023 09:43:58 +0300
>
> These are fixed in the following patch.
Thanks, LGTM. Please install on the release branch.
> >> (info "(emacs) Creating Branches")
> >> (info "(emacs) Switching Branches")
> >> (info "(emacs) Editing VC Commands")
> >
> > Mentioned, but not indexed. Please always index every command
> > described in the manual, both its name and its key binding (if any).
> > This is necessary to allow users to find the description of each
> > command quickly and easily.
> >
> > Also, vc-print-branch-log is not really described, it's just used in
> > an unrelated example of using a different feature.
>
> I can't find an existing Info node to document vc-print-branch-log.
> (info "(emacs) Branches") has such submenus:
>
> * Menu:
> * Switching Branches:: How to get to another existing branch.
> * Pulling / Pushing:: Receiving/sending changes from/to elsewhere.
> * Merging:: Transferring changes between branches.
> * Creating Branches:: How to start a new branch.
>
> Maybe vc-print-branch-log could be mentioned
> directly in (info "(emacs) Branches")?
Mentioned there, yes. But maybe it should be described in full in "VC
Change Log"?
next prev parent reply other threads:[~2023-05-25 7:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 16:16 bug#63690: 29.0.91; New vc commands missing on vc-menu Juri Linkov
2023-05-24 16:51 ` Eli Zaretskii
2023-05-24 17:31 ` Juri Linkov
2023-05-24 18:39 ` Eli Zaretskii
2023-05-25 6:43 ` Juri Linkov
2023-05-25 7:50 ` Eli Zaretskii [this message]
2023-05-25 18:25 ` Juri Linkov
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=83fs7kn927.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=63690@debbugs.gnu.org \
--cc=juri@linkov.net \
/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).