From: Carlos O'Donell <carlos@redhat.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: Carlos' patchwork queue.
Date: Thu, 27 Feb 2020 09:57:47 -0500 [thread overview]
Message-ID: <be5941a7-d632-81f8-8899-3f810dc570ae@redhat.com> (raw)
In-Reply-To: <87v9nsw19b.fsf@oldenburg2.str.redhat.com>
On 2/27/20 9:30 AM, Florian Weimer wrote:
> * Carlos O'Donell:
>
>> On 2/27/20 7:40 AM, Florian Weimer wrote:
>>> * Carlos O'Donell:
>>>
>>>> In priority order:
>>>> https://patchwork.sourceware.org/bundle/codonell/enhance-glibcsyscalls.h/
>>>
>>> This doesn't seem to work, neither with nor without being logged into
>>> Patchwork.
>>
>> I renamed it and that breaks the link. I renamed it to use 001-NNN prefixes
>> and keep my patches in review order.
>>
>> Can you view my own queue here?
>> https://patchwork.sourceware.org/user/bundles/
>
> It says: You have no bundles.
Disappointing.
I have 3 public bundles sorted by me in review order.
http://patchwork.sourceware.org/bundle/codonell/01-enhance-glibcsyscalls.h/
http://patchwork.sourceware.org/bundle/codonell/02-dt-audit/
http://patchwork.sourceware.org/bundle/codonell/03-tldsec-reservation/
I like the concept of a public review queue. It makes me more accountable
to all of you for what I'm working on and the order.
In my own weekly review I account for who and which organizations I'm
reviewing patches for, just to make sure I'm trying to keep my review
queue open to new submitters.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2020-02-27 14:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-23 18:06 Carlos' patchwork queue Carlos O'Donell
2020-02-27 12:40 ` Florian Weimer
2020-02-27 14:15 ` Carlos O'Donell
2020-02-27 14:30 ` Florian Weimer
2020-02-27 14:57 ` Carlos O'Donell [this message]
2020-02-27 18:52 ` Tulio Magno Quites Machado Filho
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=be5941a7-d632-81f8-8899-3f810dc570ae@redhat.com \
--to=carlos@redhat.com \
--cc=fweimer@redhat.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).