From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: proposal for branch patches after first release
Date: Thu, 29 Nov 2012 16:14:00 -0000 [thread overview]
Message-ID: <83wqx4v12l.fsf@gnu.org> (raw)
In-Reply-To: <20121129141415.GJ3540@adacore.com>
> Date: Thu, 29 Nov 2012 15:14:15 +0100
> From: Joel Brobecker <brobecker@adacore.com>
>
> The proposal:
>
> Once a release has been published off a branch, any patch merged
> on the release branch requires a corresponding update in the
> NEWS file.
That'd be a nuisance, IMO, because some of them might be
NEWS-unworthy.
An alternative would be to require some predictably formatted string
in the log entry or the commit message, which you then could grep for.
Yet another alternative would be to have a separate file, which
doesn't get into the tarball, with the relevant info, and request each
commit to the branch be accompanied with an entry for that file.
next prev parent reply other threads:[~2012-11-29 16:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 14:14 Joel Brobecker
2012-11-29 16:14 ` Eli Zaretskii [this message]
2012-11-29 16:32 ` Pedro Alves
2012-11-29 21:04 ` Joel Brobecker
2012-11-30 9:15 ` Eli Zaretskii
2012-11-30 10:55 ` Pedro Alves
2012-12-07 21:16 ` Tom Tromey
2012-12-03 6:51 ` Doug Evans
2012-12-03 9:16 ` Joel Brobecker
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=83wqx4v12l.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.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