From: Ihor Radchenko <yantar92@gmail.com>
To: Robert Pluim <rpluim@gmail.com>
Cc: Karl Fogel <kfogel@red-bean.com>, Org Mode <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] CONTRIBUTE: Link WORG page when explaining commit message format
Date: Sat, 16 Apr 2022 17:35:22 +0800 [thread overview]
Message-ID: <87bkx1nzfp.fsf@localhost> (raw)
In-Reply-To: <87tuau3440.fsf@gmail.com>
Robert Pluim <rpluim@gmail.com> writes:
> It might be good to mention `magit-generate-changelog' there as an
> easy way to produce the ChangeLog format entry (it doesnʼt require you
> to iterate over the diff hunks, and you can call it from the magit
> commit buffer).
Note that we already mention `magit-commit-add-log` in
https://orgmode.org/worg/org-contribute.html#commit-messages
I personally dislike magit-generate-changelog because it tempts to
document only a single change in a function, even when multiple changes
were made in that function.
However, the command might indeed be useful for others. It could be a
good addition to https://orgmode.org/worg/org-contribute.org I do not
think that magit staff belongs to CONTRIBUTE file directly.
Patches are welcome.
Best,
Ihor
next prev parent reply other threads:[~2022-04-16 9:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-04 20:53 Removing obsolete function `org-truely-invisible-p' Karl Fogel
2021-12-04 22:19 ` Samuel Wales
2021-12-19 9:14 ` Ihor Radchenko
2022-04-01 0:28 ` Karl Fogel
2022-04-04 11:55 ` Ihor Radchenko
2022-04-04 16:20 ` Karl Fogel
2022-04-05 6:14 ` Ihor Radchenko
2022-04-05 17:08 ` Linking by Message-ID Max Nikulin
2022-04-05 18:41 ` Removing obsolete function `org-truely-invisible-p' Karl Fogel
2022-04-07 4:59 ` Ihor Radchenko
2022-04-07 16:57 ` Karl Fogel
2022-04-15 9:33 ` [PATCH] CONTRIBUTE: Link WORG page when explaining commit message format Ihor Radchenko
2022-04-15 12:47 ` Robert Pluim
2022-04-15 21:13 ` Karl Fogel
2022-04-16 9:35 ` Ihor Radchenko [this message]
2022-04-23 8:06 ` Ihor Radchenko
2022-04-23 15:47 ` Karl Fogel
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=87bkx1nzfp.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=kfogel@red-bean.com \
--cc=rpluim@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).