From: Joseph Myers <joseph@codesourcery.com>
To: Carlos O'Donell <carlos@redhat.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: Review promise :-)
Date: Thu, 13 Feb 2020 20:54:18 +0000 [thread overview]
Message-ID: <alpine.DEB.2.21.2002132050340.22316@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAEMqeSrQETD85WY7pfAEsoFtBLYX72kmbwtpxEuYbKbJtMCB6g@mail.gmail.com>
On Thu, 13 Feb 2020, Carlos O'Donell wrote:
> The hard part is that each developers queue is messy because we don't
> keep them clean.
One benefit we were supposed to get from stopping manual ChangeLog edits
was that the git-patch-id of a commit for a patch committed with no
changes would match the git-patch-id of the patch posted to the mailing
list - and so patchwork would be able to mark such a patch as committed
automatically.
I'm not clear if this is a standard patchwork feature or just something we
hoped to be able to implement after stopping manual ChangeLog edits,
however.
(It might make sense to clean up existing patches in patchwork based on
having a git-patch-id matching a change that is now on master, as well as
doing such cleanup automatically in future.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2020-02-13 20:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 14:56 Review promise :-) Carlos O'Donell
2020-02-13 15:03 ` Florian Weimer
2020-02-13 15:06 ` Carlos O'Donell
2020-02-13 15:44 ` Siddhesh Poyarekar
2020-02-13 15:47 ` Siddhesh Poyarekar
2020-02-13 16:01 ` Zack Weinberg
2020-02-13 16:17 ` Florian Weimer
2020-02-13 16:19 ` Carlos O'Donell
2020-02-13 17:42 ` Zack Weinberg
2020-02-13 17:57 ` Florian Weimer
2020-02-13 18:12 ` Zack Weinberg
[not found] ` <CAKCAbMi9bejmEgsrQcHau0uwU8Dc42FwFz3Wf6-4Qxyw4WE1hw@mail.gmail.com>
2020-02-13 18:20 ` Carlos O'Donell
2020-02-13 18:31 ` Zack Weinberg
2020-02-14 8:43 ` Stefan Liebler
2020-02-14 16:48 ` Carlos O'Donell
2020-02-17 7:38 ` Stefan Liebler
2020-02-13 20:54 ` Joseph Myers [this message]
2020-02-14 1:12 ` Carlos O'Donell
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=alpine.DEB.2.21.2002132050340.22316@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=carlos@redhat.com \
--cc=libc-alpha@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).