From: Carlos O'Donell <carlos@redhat.com>
To: Stefan Liebler <stli@linux.ibm.com>, libc-alpha@sourceware.org
Subject: Re: Review promise :-)
Date: Fri, 14 Feb 2020 11:48:32 -0500 [thread overview]
Message-ID: <6b193815-f19e-089b-657b-f26ad974df38@redhat.com> (raw)
In-Reply-To: <5cf39f78-902c-a1a6-f91d-9325cf59a773@linux.ibm.com>
On 2/14/20 3:43 AM, Stefan Liebler wrote:
> On 2/13/20 7:31 PM, Zack Weinberg wrote:
>> On Thu, Feb 13, 2020 at 1:21 PM Carlos O'Donell <carlos@redhat.com> wrote:
>>>> To avoid further round-trips, here is a screenshot of everything I can
>>>> see on a search results page. (My actual queue is three pages long,
>>>> this is a very small subset.)
>>>
>>> Fixed.
>>>
>>> You need to be a listed project maintainer to be able to edit patch status.
>>
>> Thanks, it works now. (It's a little odd that _bulk_ edits require
>> this privilege but edits on individual patches don't, but that's
>> probably something to take up with patchwork upstream.)
>>
>> zw
>>
>
> Carlos,
>
> Can you please help. I see the checkboxes, but it seems as I only have the option to "Create bundle" at the bottom of the page or change each single patch.
>
> Its not clear to me where I have to be listed?
> - https://sourceware.org/glibc/wiki/MAINTAINERS
> (here I am listed)
> - https://patchwork.sourceware.org/project/glibc/
> (here I am not listed in the maintainers box. Is this the missing piece? If yes, can you please add me.)
>
> Another hint:
> I had created my patchwork account with stli@linux.vnet.ibm.com .
> In the meantime I use stli@linux.ibm.com .
> I've just also linked stli@linux.ibm.com to the patchwork account.
I just added you as a maintainer. Should be fixed now. Tell me if it's not.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2020-02-14 16:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 14:56 Review promise :-) Carlos O'Donell
2020-02-13 15:03 ` Florian Weimer
2020-02-13 15:06 ` Carlos O'Donell
2020-02-13 15:44 ` Siddhesh Poyarekar
2020-02-13 15:47 ` Siddhesh Poyarekar
2020-02-13 16:01 ` Zack Weinberg
2020-02-13 16:17 ` Florian Weimer
2020-02-13 16:19 ` Carlos O'Donell
2020-02-13 17:42 ` Zack Weinberg
2020-02-13 17:57 ` Florian Weimer
2020-02-13 18:12 ` Zack Weinberg
[not found] ` <CAKCAbMi9bejmEgsrQcHau0uwU8Dc42FwFz3Wf6-4Qxyw4WE1hw@mail.gmail.com>
2020-02-13 18:20 ` Carlos O'Donell
2020-02-13 18:31 ` Zack Weinberg
2020-02-14 8:43 ` Stefan Liebler
2020-02-14 16:48 ` Carlos O'Donell [this message]
2020-02-17 7:38 ` Stefan Liebler
2020-02-13 20:54 ` Joseph Myers
2020-02-14 1:12 ` 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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6b193815-f19e-089b-657b-f26ad974df38@redhat.com \
--to=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=stli@linux.ibm.com \
/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).