From: Lars Ingebrigtsen <larsi@gnus.org>
To: npostavs@users.sourceforge.net
Cc: 20670@debbugs.gnu.org, ding@gnus.org, Nikolaus@rath.org
Subject: Re: bug#20670: [PATCH] nnimap: enable additional expunge options (v3)
Date: Wed, 25 Jan 2017 01:25:21 +0100 [thread overview]
Message-ID: <87mveg9ea6.fsf@gnus.org> (raw)
In-Reply-To: <87lgu0t2ae.fsf@users.sourceforge.net> (npostavs's message of "Tue, 24 Jan 2017 19:24:09 -0500")
npostavs@users.sourceforge.net writes:
> Nikolaus Rath <Nikolaus@rath.org> writes:
>
>>
>> Btw, is there any way to generate the list of affected functions in the
>> commit message automatically? Doing this by hand is rather cumbersome...
>
> See "Generating ChangeLog entries" in CONTRIBUTE.
Didn't see anything there to put all changed functions into a ChangeLog
automatically?
> If you think it's not
> good enough, see also https://github.com/magit/magit/issues/2931 and
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=16301.
So ... the answer is no? :-)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2017-01-25 0:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <556538A5.3050302@rath.org>
2015-07-04 3:28 ` Nikolaus Rath
2017-01-24 19:35 ` bug#20670: " Lars Ingebrigtsen
2017-01-24 23:37 ` Nikolaus Rath
2017-01-24 23:46 ` Lars Ingebrigtsen
2017-01-25 0:18 ` Lars Ingebrigtsen
2017-01-25 0:22 ` Nikolaus Rath
2017-01-25 0:23 ` Lars Ingebrigtsen
2017-01-25 0:32 ` Nikolaus Rath
2017-01-25 16:45 ` Lars Ingebrigtsen
2019-09-26 23:41 ` Lars Ingebrigtsen
2017-01-25 0:24 ` npostavs
2017-01-25 0:25 ` Lars Ingebrigtsen [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mveg9ea6.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=20670@debbugs.gnu.org \
--cc=Nikolaus@rath.org \
--cc=ding@gnus.org \
--cc=npostavs@users.sourceforge.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.
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 NNTP newsgroup(s).