From: Florian Weimer <fw@deneb.enyo.de>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>
Cc: 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: Thu, 28 Nov 2019 16:24:00 -0000 [thread overview]
Message-ID: <874kyo7yw1.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <e2c16c03-64d0-7651-1078-a707af916316@gotplt.org> (Siddhesh Poyarekar's message of "Thu, 28 Nov 2019 21:39:06 +0530")
* 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.
next prev parent reply other threads:[~2019-11-28 16:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 5:01 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:27 ` Siddhesh Poyarekar
2019-12-03 19:07 ` Tom Tromey
2019-12-04 1:06 ` Carlos O'Donell
2019-11-28 15:45 ` Carlos O'Donell
2019-11-28 16:03 ` Florian Weimer
2019-11-28 16:09 ` Siddhesh Poyarekar
2019-11-28 16:24 ` Florian Weimer [this message]
2019-11-29 12:52 ` Andrew Burgess
2019-11-28 16:24 ` Carlos O'Donell
2019-11-28 16:45 ` Siddhesh Poyarekar
2019-12-08 12:07 ` 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 17:00 ` Siddhesh Poyarekar
2019-12-09 15:44 ` Sergio Durigan Junior
2019-12-09 16:57 ` Siddhesh Poyarekar
2019-12-09 17:15 ` Sergio Durigan Junior
2020-01-14 19:46 ` Christian Biesinger via gdb-patches
2020-01-15 3:18 ` 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=874kyo7yw1.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--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).