From: Rical Jasan <ricaljasan@pacific.net>
To: Carlos O'Donell <carlos@redhat.com>,
Joseph Myers <joseph@codesourcery.com>
Cc: libc-alpha <libc-alpha@sourceware.org>
Subject: Re: Last Responder Wins in Patchwork?
Date: Sat, 27 May 2017 11:36:00 -0000 [thread overview]
Message-ID: <cc75a497-af4e-c811-dd03-568667b0505d@pacific.net> (raw)
In-Reply-To: <f4336d23-eebe-caf9-fbb4-5845dca81390@redhat.com>
Sorry to revive an old thread, but I finally had time to roam around
some more in patchwork, and have some follow up.
On 11/30/2016 06:03 AM, Carlos O'Donell wrote:
> On 11/30/2016 07:56 AM, Joseph Myers wrote:
>> On Wed, 30 Nov 2016, Rical Jasan wrote:
>>> Why does this say I'm the submitter?
>>>
>>> https://patchwork.sourceware.org/patch/12829/
>>
>> Because the message it is based on is one where you included a patch.
>> Note the "I've attached the beginnings of how I would approach it" in the
>> first message shown.
Seems that even text in the message that looks like a diff incurs a
patch in patchwork:
https://patchwork.sourceware.org/patch/20500/
That's brutal.
> Mark it RFC if that's what is is, and then re-post a new patch
> under a new thread if that's the way you want to go.
>
> https://sourceware.org/glibc/wiki/Patch%20Review%20Workflow
"Not Applicable" is probably better in both the above cases, I think.
I'll be updating all my noise in the patchwork queue shortly.
Rical
prev parent reply other threads:[~2017-05-27 11:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 9:44 Rical Jasan
2016-11-30 12:57 ` Joseph Myers
2016-11-30 14:03 ` Carlos O'Donell
2017-05-27 11:36 ` Rical Jasan [this message]
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=cc75a497-af4e-c811-dd03-568667b0505d@pacific.net \
--to=ricaljasan@pacific.net \
--cc=carlos@redhat.com \
--cc=joseph@codesourcery.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).