From: Florian Weimer <fweimer@redhat.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [RFC] Updating patchwork patches on commit
Date: Mon, 07 Dec 2020 09:45:54 +0100 [thread overview]
Message-ID: <878saam2bh.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <e52f712f-cf7b-879d-6c55-d00d106780af@gotplt.org> (Siddhesh Poyarekar's message of "Mon, 7 Dec 2020 11:18:22 +0530")
* Siddhesh Poyarekar:
> We could achieve this without additional busy work by having the git
> hook send out [pushed] emails to the list in addition to glibc-cvs
> (libc-alpha should be spared the private branch traffic of course)
> whenever it sees a commit that it can't find on patchwork. A nightly
> script can then trivially mark all [pushed] patches as committed.
I'm not sure if this useful if we can't find the thread to which the
updated commit belongs.
If we can find the thread, it would be more useful to patch the diff
between what was committed and the latest posted patch.
Thanks,
Florian
--
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill
next prev parent reply other threads:[~2020-12-07 8:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 5:48 Siddhesh Poyarekar
2020-12-07 8:45 ` Florian Weimer [this message]
2020-12-07 9:30 ` Siddhesh Poyarekar
2020-12-07 16:15 ` DJ Delorie
2020-12-07 16:39 ` Siddhesh Poyarekar
2020-12-07 17:02 ` DJ Delorie
2020-12-07 18:11 ` Joseph Myers
2020-12-08 2:57 ` Siddhesh Poyarekar
2020-12-08 9:08 ` Andreas Schwab
2020-12-08 10:10 ` Siddhesh Poyarekar
2020-12-16 18:35 ` Girish Joshi
2020-12-16 18:49 ` Siddhesh Poyarekar
2020-12-17 17:49 ` Girish Joshi
2020-12-18 4:04 ` Siddhesh Poyarekar
2020-12-19 13:25 ` Girish Joshi
2020-12-22 15:13 ` Girish Joshi
2021-01-06 20:26 ` Girish Joshi
2021-02-04 15:47 ` Girish Joshi
2021-02-12 5:25 ` Siddhesh Poyarekar
2021-02-12 9:02 ` Siddhesh Poyarekar
2021-02-12 13:04 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878saam2bh.fsf@oldenburg2.str.redhat.com \
--to=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).