From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: GLIBC Devel <libc-alpha@sourceware.org>,
gdb-patches@sourceware.org, help-guix@gnu.org
Subject: Re: [X-POST] patchwork.sourceware.org refresh
Date: Sun, 1 Dec 2019 10:05:18 +0530 [thread overview]
Message-ID: <48174ee5-39e3-85a2-d420-008c27266179@gotplt.org> (raw)
In-Reply-To: <alpine.LFD.2.21.1911301128120.3472978@eddie.linux-mips.org>
On 30/11/19 5:05 pm, Maciej W. Rozycki wrote:
> How do I do that though? There doesn't appear to be anything there I
> could do from my profile page or elsewhere.
Oh I was only thinking of something rudimentary like copying over the
list of pending patches into a text file.
> Sure, and greatly appreciated too (I've seen your proposal in the other
> thread of discussion), but adding hooks is not supposed to affect any
> existing patchwork state that the lone upgrade puts at risk. Some kind of
> restructuring could.
Yeah, I hope it works out without having to nuke the repo too. I'll
find out later today.
Siddhesh
next prev parent reply other threads:[~2019-12-01 4:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <78c774ef-9f9c-3339-aeb8-84636ee94360@gotplt.org>
2019-11-28 5:04 ` Fwd: [X-POST] patchwork.sourceware.org refresh Siddhesh Poyarekar
[not found] ` <alpine.LFD.2.21.1911280509420.3472978@eddie.linux-mips.org>
2019-11-28 5:47 ` Siddhesh Poyarekar
2019-11-28 15:47 ` Carlos O'Donell
2019-11-30 11:35 ` Maciej W. Rozycki
2019-12-01 4:35 ` Siddhesh Poyarekar [this message]
2019-12-01 16:26 ` Siddhesh Poyarekar
2019-12-03 19:07 ` Tom Tromey
2019-12-04 1:05 ` Carlos O'Donell
2019-12-08 12:06 ` Siddhesh Poyarekar
2019-12-08 12:10 ` Florian Weimer
2019-12-08 12:21 ` Christian Brauner
2019-12-09 7:56 ` Siddhesh Poyarekar
2019-12-09 16:52 ` Konstantin Ryabitsev
2019-12-09 16:59 ` Siddhesh Poyarekar
2019-12-09 15:44 ` Sergio Durigan Junior
2019-12-09 16:56 ` Siddhesh Poyarekar
2019-12-09 17:15 ` Sergio Durigan Junior
2020-01-14 19:05 ` Christian Biesinger
2020-01-15 2:33 ` 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=48174ee5-39e3-85a2-d420-008c27266179@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=gdb-patches@sourceware.org \
--cc=help-guix@gnu.org \
--cc=libc-alpha@sourceware.org \
--cc=macro@linux-mips.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.