From: Florian Weimer <fw@deneb.enyo.de>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>
Cc: GLIBC Devel <libc-alpha@sourceware.org>
Subject: Re: Sourceware patchwork instance is up
Date: Mon, 04 May 2020 14:40:30 +0200 [thread overview]
Message-ID: <87eerzvpoh.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <fd33690f-a2a0-62b9-a225-427515629714@gotplt.org> (Siddhesh Poyarekar's message of "Thu, 30 Apr 2020 08:22:59 +0530")
* Siddhesh Poyarekar:
> Here's a quick rundown on status:
>
> - The instance is based on the tip of the 2.2 stable branch
>
> - The instance handles DMARC related issues well as is evident from the
> patches I imported manuall
Thanks. It seems that patchwork does not understand scissors:
<https://patchwork.sourceware.org/project/glibc/patch/87d07p9v73.fsf@mid.deneb.enyo.de/>
The subsequent patches just ended up as comments under the first
patch, instead of creating a new patch.
Was this different before? I cannot remember.
next prev parent reply other threads:[~2020-05-04 12:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 2:52 Siddhesh Poyarekar
2020-05-04 12:40 ` Florian Weimer [this message]
2020-05-04 18:59 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eerzvpoh.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--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).