From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Bruno Haible <bruno@clisp.org>, bug-gnulib@gnu.org
Subject: Re: [PATCH 0/3] vcs-to-changelog fixes
Date: Fri, 17 Jan 2020 09:09:17 +0530 [thread overview]
Message-ID: <ec6caa14-bbbb-1323-d2ec-73aa569e7e04@gotplt.org> (raw)
In-Reply-To: <32904187.eT0rVSdmTd@omega>
On 17/01/20 2:02 am, Bruno Haible wrote:
> For the first one, in gnulib, it's customary to reference, in the ChangeLog
> entry, the report (mail or bug report) where which sollicited the change.
> I added it.
Got it, I'll keep that in mind.
Thanks,
Siddhesh
prev parent reply other threads:[~2020-01-17 3:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 7:19 [PATCH 0/3] vcs-to-changelog fixes Siddhesh Poyarekar
2020-01-16 7:19 ` [PATCH 1/3] vcs-to-changelog: Drop python3 shebang from frontend_c.py Siddhesh Poyarekar
2020-01-16 7:19 ` [PATCH 2/3] vcs-to-changelog: Fix formatting of ChangeLog ouput Siddhesh Poyarekar
2020-01-16 7:19 ` [PATCH 3/3] vcs-to-changelog: Allow loading of custom quirks file Siddhesh Poyarekar
2020-01-16 20:32 ` [PATCH 0/3] vcs-to-changelog fixes Bruno Haible
2020-01-17 3:39 ` Siddhesh Poyarekar [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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ec6caa14-bbbb-1323-d2ec-73aa569e7e04@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).