From: Florian Weimer <fw@deneb.enyo.de>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: Siddhesh Poyarekar <siddhesh@gotplt.org>,
Carlos O'Donell <codonell@redhat.com>,
GLIBC Devel <libc-alpha@sourceware.org>,
gdb-patches@sourceware.org, info-guix@gnu.org
Subject: Re: [X-POST] patchwork.sourceware.org refresh
Date: Fri, 29 Nov 2019 14:24:30 +0100 [thread overview]
Message-ID: <87tv6mak8h.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20191129125200.GG3410@embecosm.com> (Andrew Burgess's message of "Fri, 29 Nov 2019 12:52:00 +0000")
[-- Attachment #1: Type: text/plain, Size: 934 bytes --]
* Andrew Burgess:
> * Florian Weimer <fw@deneb.enyo.de> [2019-11-28 17:23:58 +0100]:
>
>> * Siddhesh Poyarekar:
>>
>> > On 28/11/19 9:32 pm, Florian Weimer wrote:
>> >> We should make sure that we can figure out what URLs refer to. I
>> >> found one in the commit log:
>> >>
>> >> <https://patchwork.sourceware.org/patch/10342/>
>> >>
>> >
>> > Hmm, that's going to be a bit of a challenge. Let me see what I can do.
>>
>> Maybe it's possible to grep the backing files for the message ID?
>> Then we have at least *something* to resolve the URL in case we need
>> it in the future.
>
> If there aren't too many references, maybe you could dump the patch
> information into a text file within the source tree?
I think just posting it to the mailing list would be sufficient.
Below is the (compressed) output from:
mysql -u patchwork -p -B -e "SELECT id, msgid FROM patchwork_patch" patchwork
I think this is all we need.
[-- Attachment #2: patches.txt.gz --]
[-- Type: application/gzip, Size: 556784 bytes --]
next prev parent reply other threads:[~2019-11-29 13:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 5:00 [X-POST] patchwork.sourceware.org refresh Siddhesh Poyarekar
2019-11-28 5:11 ` Simon Marchi
2019-11-28 5:25 ` Maciej W. Rozycki
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
2019-12-01 16:26 ` Siddhesh Poyarekar
2019-12-03 19:07 ` Tom Tromey
2019-12-04 1:05 ` Carlos O'Donell
2019-11-28 15:45 ` Carlos O'Donell
2019-11-28 16:02 ` Florian Weimer
2019-11-28 16:09 ` Siddhesh Poyarekar
2019-11-28 16:23 ` Florian Weimer
2019-11-29 12:52 ` Andrew Burgess
2019-11-29 13:24 ` Florian Weimer [this message]
2019-11-28 16:24 ` Carlos O'Donell
2019-11-28 16:44 ` Siddhesh Poyarekar
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
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=87tv6mak8h.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=andrew.burgess@embecosm.com \
--cc=codonell@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=info-guix@gnu.org \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@gotplt.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).