This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
* 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:
patches.txt.gz
Description: application/gzip
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |