From: Kyle Meyer <kyle@kyleam.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: changelog entry via Magit (was Bug: Typo in archive location example in manual)
Date: Sun, 13 Sep 2020 12:54:07 -0400 [thread overview]
Message-ID: <87bli9mxcg.fsf@kyleam.com> (raw)
In-Reply-To: <87zh5ub6d5.fsf@localhost>
Ihor Radchenko writes:
> By the way, do you know how to automatically format changelog entries in
> magit. The suggestion from contribute page seems outdated (or I miss
> something):
>
>> If you are using magit.el in Emacs, the ChangeLog for such entries are
>> easily produced by pressing C in the diff listing.
Hmm, that's what I use. If you go to the diff buffer that (by default)
is popped up while committing [*], hitting C (magit-commit-add-log) on a
hunk should add an entry to the commit message buffer.
What happens on your end? (And what version of Magit are you using?)
[*] I haven't followed it closely, but Noam Postavsky has worked on
improving changelog generation in Emacs (shipped with Emacs 27, I
believe) and then using that in Magit (in-flight PR). IIUC the
end result is that the full changelog skeleton could be inserted
by calling a single command from the commit message buffer. (And
calling the command manually could be avoided by adding it to
git-commit-setup-hook.)
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=16301#11
https://github.com/magit/magit/issues/2931
https://github.com/magit/magit/pull/3928
next prev parent reply other threads:[~2020-09-13 16:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-13 3:54 Bug: Typo in archive location example in manual [9.3.7 (release_9.3.7-807-gf1363d @ /home/yantar92/.emacs.d/straight/build/org/)] Ihor Radchenko
2020-09-13 4:53 ` Kyle Meyer
2020-09-13 5:20 ` Ihor Radchenko
2020-09-13 16:48 ` Bastien
2020-09-13 16:54 ` Kyle Meyer [this message]
2020-09-13 17:12 ` changelog entry via Magit (was Bug: Typo in archive location example in manual) Bastien
2020-09-14 7:16 ` Ihor Radchenko
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bli9mxcg.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@gmail.com \
/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/org-mode.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).