public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: DJ Delorie <dj@redhat.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [RFC] Auto-posting committed patches to this list?
Date: Wed, 10 Mar 2021 23:33:20 -0500	[thread overview]
Message-ID: <xn35x2qpgv.fsf@rhel8.vm> (raw)
In-Reply-To: <0d14c1fb-6f72-9b48-cea5-4a40c1da5635@gotplt.org> (message from Siddhesh Poyarekar on Tue, 9 Mar 2021 23:58:39 +0530)


How much of the problem space would be solved if we only emailed commit
"patches" directly to the patchwork system?  And how difficult would it
be to get patchwork to properly match independent commit mails to
existing patch series?


  reply	other threads:[~2021-03-11  4:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-09 18:28 Siddhesh Poyarekar
2021-03-11  4:33 ` DJ Delorie [this message]
2021-03-11  6:36   ` Siddhesh Poyarekar
2021-03-11 16:37     ` DJ Delorie
2021-03-15  2:52       ` Siddhesh Poyarekar
2021-03-15 14:59 ` Paul Zimmermann
2021-03-15 15:02   ` Siddhesh Poyarekar
2021-03-16  2:24 ` Carlos O'Donell
2021-03-16  3:52   ` Siddhesh Poyarekar
2021-03-16  3:55     ` 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=xn35x2qpgv.fsf@rhel8.vm \
    --to=dj@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).