* Last Responder Wins in Patchwork?
@ 2016-11-30 9:44 Rical Jasan
2016-11-30 12:57 ` Joseph Myers
0 siblings, 1 reply; 4+ messages in thread
From: Rical Jasan @ 2016-11-30 9:44 UTC (permalink / raw)
To: libc-alpha
Why does this say I'm the submitter?
https://patchwork.sourceware.org/patch/12829/
It's been kind of a late night, but things shouldn't be that weird...
does anybody else see that?
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Last Responder Wins in Patchwork?
2016-11-30 9:44 Last Responder Wins in Patchwork? Rical Jasan
@ 2016-11-30 12:57 ` Joseph Myers
2016-11-30 14:03 ` Carlos O'Donell
0 siblings, 1 reply; 4+ messages in thread
From: Joseph Myers @ 2016-11-30 12:57 UTC (permalink / raw)
To: Rical Jasan; +Cc: libc-alpha
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.
--
Joseph S. Myers
joseph@codesourcery.com
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Last Responder Wins in Patchwork?
2016-11-30 12:57 ` Joseph Myers
@ 2016-11-30 14:03 ` Carlos O'Donell
2017-05-27 11:36 ` Rical Jasan
0 siblings, 1 reply; 4+ messages in thread
From: Carlos O'Donell @ 2016-11-30 14:03 UTC (permalink / raw)
To: Joseph Myers, Rical Jasan; +Cc: libc-alpha
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.
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
--
Cheers,
Carlos.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Last Responder Wins in Patchwork?
2016-11-30 14:03 ` Carlos O'Donell
@ 2017-05-27 11:36 ` Rical Jasan
0 siblings, 0 replies; 4+ messages in thread
From: Rical Jasan @ 2017-05-27 11:36 UTC (permalink / raw)
To: Carlos O'Donell, Joseph Myers; +Cc: libc-alpha
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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2017-05-27 11:36 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-11-30 9:44 Last Responder Wins in Patchwork? 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 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).