From: "Gabriel F. T. Gomes" <gabriel@inconstante.net.br>
To: Florian Weimer <fweimer@redhat.com>
Cc: Siddhesh Poyarekar <siddhesh@gotplt.org>,
Carlos O'Donell <carlos@redhat.com>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>,
<libc-alpha@sourceware.org>
Subject: Re: When can we stop writing ChangeLogs?
Date: Thu, 3 Oct 2019 22:37:09 -0300 [thread overview]
Message-ID: <20191003223709.4b6e1c40@tereshkova> (raw)
In-Reply-To: <87tv8ty3iv.fsf@oldenburg2.str.redhat.com>
On Mon, 30 Sep 2019, Florian Weimer wrote:
>* Siddhesh Poyarekar:
>
>> On 30/09/19 2:36 pm, Florian Weimer wrote:
>>> I'm looking for something far simpler here—a script that submitters and
>>> reviewers can run to see what's going to be committed, and some level of
>>> project consensus that this is how patches should be posted.
>>
>> What kind of scripting are you thinking of? pwclient should be able to
>> download a patch from patchwork and apply it, giving you an indication
>> of what a patch is going to look like.
>
>The patch isn't the problem. It's the commit subject, author and commit
>message that I'm after.
Supposing that patches created with git format-patch are posted, which can
then be applied with git am --scissors, do you foresee any problems with
Reviewed-by statements and friends? I mean, are you trying to match
[exactly] the patch on the mailing list with the patch that has been
actually committed.
next prev parent reply other threads:[~2019-10-04 1:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 18:55 When can we stop writing ChangeLogs? Siddhesh Poyarekar
2019-09-24 23:21 ` Adhemerval Zanella
2019-09-28 3:16 ` Carlos O'Donell
2019-09-30 14:30 ` Siddhesh Poyarekar
2019-09-30 15:56 ` Florian Weimer
2019-09-30 16:56 ` Siddhesh Poyarekar
2019-09-30 18:36 ` Florian Weimer
2019-09-30 19:27 ` Siddhesh Poyarekar
2019-09-30 19:42 ` Florian Weimer
2019-10-04 1:37 ` Gabriel F. T. Gomes [this message]
2019-10-07 2:27 ` Carlos O'Donell
2019-10-07 9:05 ` Florian Weimer
2019-10-07 9:40 ` Maciej W. Rozycki
2019-10-07 9:47 ` Florian Weimer
2019-09-30 19:31 ` Carlos O'Donell
2019-09-30 19:39 ` Siddhesh Poyarekar
2019-09-30 19:41 ` Joseph Myers
2019-09-30 19:53 ` Carlos O'Donell
2019-10-01 17:41 ` Florian Weimer
2019-10-01 20:18 ` Joseph Myers
2019-10-02 9:30 ` Florian Weimer
2019-09-30 19:52 ` Maciej W. Rozycki
2019-10-07 12:56 ` Florian Weimer
2019-10-07 13:31 ` Florian Weimer
2019-10-07 14:49 ` Siddhesh Poyarekar
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.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191003223709.4b6e1c40@tereshkova \
--to=gabriel@inconstante.net.br \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@gotplt.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).