From: "Martin Liška" <mliska@suse.cz>
To: Jakub Jelinek <jakub@redhat.com>, Georg-Johann Lay <avr@gjlay.de>
Cc: gcc@gcc.gnu.org, overseers@sourceware.org,
"Frank Ch. Eigler" <fche@elastic.org>
Subject: Re: subversion status on gcc.gnu.org
Date: Fri, 3 Apr 2020 10:38:17 +0200 [thread overview]
Message-ID: <aa666c03-8d6b-e827-6364-2af759a60f70@suse.cz> (raw)
In-Reply-To: <20200402122615.GT2212@tucnak>
[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]
On 4/2/20 2:26 PM, Jakub Jelinek via Gcc wrote:
> On Thu, Apr 02, 2020 at 02:19:10PM +0200, Georg-Johann Lay wrote:
>> Am 20.03.20 um 18:37 schrieb Frank Ch. Eigler via Gcc:
>>> Hi -
>>>
>>> Both svn: and ssh+svn: now work for your archeological needs.
>>> Further, URLs such as
>>>
>>> https://gcc.gnu.org/viewcvs?rev=279160&root=gcc&view=rev
>>> https://gcc.gnu.org/r123456
>>>
>>> are mapped to gitweb searches that try to locate the matching
>>> From-SVN: rABCDEF commit. This way, historical URLs from bugzilla
>>> should work.
>>
>> This does not work as expected. For example,
>>
>> https://gcc.gnu.org/r2000
>>
>> maps to a search and you get thousands of hits for SVN: r2000**
>
> The gcc git svn-rev alias handles that (and also handles release and other
> branches) using approx.
> git log --all --grep="From-SVN: r$rev\b" | head -n 1 | awk '{print $2}'
> where $rev is 2000 in your case.
>
> Jakub
>
Btw. what about statically generated database (files) which can be used for redirection?
I'm sending an example and I have a script that can generate any file content.
Martin
[-- Attachment #2: svn-to-git-mapping.tar.bz2 --]
[-- Type: application/x-bzip, Size: 1359 bytes --]
next prev parent reply other threads:[~2020-04-03 8:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 17:37 Frank Ch. Eigler
2020-03-24 16:51 ` Peter Bergner
2020-03-24 17:06 ` Frank Ch. Eigler
2020-03-24 17:12 ` Peter Bergner
2020-03-24 20:53 ` Gerald Pfeifer
2020-03-24 21:02 ` Frank Ch. Eigler
2020-03-29 14:14 ` Martin Liška
2020-04-02 12:19 ` Georg-Johann Lay
2020-04-02 12:26 ` Jakub Jelinek
2020-04-03 8:38 ` Martin Liška [this message]
2020-04-03 8:54 ` Jakub Jelinek
2020-04-03 9:23 ` Martin Liška
2020-04-03 13:44 ` Martin Liška
2020-04-03 20:19 ` Frank Ch. Eigler
2020-04-04 6:38 ` Martin Liška
2020-04-05 23:57 ` Frank Ch. Eigler
2020-04-06 8:09 ` Martin Liška
2020-04-06 8:37 ` Jakub Jelinek
2020-04-06 8:46 ` Martin Liška
2020-04-06 8:55 ` Jakub Jelinek
2020-04-06 8:59 ` Martin Liška
2020-04-06 9:15 ` Andreas Schwab
2020-04-06 9:36 ` Andrew Pinski
2020-04-06 15:04 ` Joseph Myers
2020-04-07 7:13 ` Martin Liška
2020-04-07 7:22 ` Andreas Schwab
2020-04-07 7:29 ` Martin Liška
2020-04-07 7:42 ` Martin Liška
2020-04-07 14:09 ` Frank Ch. Eigler
2020-04-07 14:22 ` Martin Liška
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=aa666c03-8d6b-e827-6364-2af759a60f70@suse.cz \
--to=mliska@suse.cz \
--cc=avr@gjlay.de \
--cc=fche@elastic.org \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=overseers@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).