public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: Jakub Jelinek <jakub@redhat.com>
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 15:44:40 +0200	[thread overview]
Message-ID: <b2a001df-820e-1d3d-65b5-89ef2992b1b2@suse.cz> (raw)
In-Reply-To: <f60f7362-c607-d09d-5282-0462b307f996@suse.cz>

On 4/3/20 11:23 AM, Martin Liška wrote:
> On 4/3/20 10:54 AM, Jakub Jelinek wrote:
>> On Fri, Apr 03, 2020 at 10:38:17AM +0200, Martin Liška wrote:
>>>> 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.
>>
>> That can work too, but do we want a directory with 280156 files?
> 
> It's not ideal :) Maybe a modern linux filesystem will not suffer so much?
> Oversees people can tell what they want.
> 
>>  One way is
>> to split the number into halves and have files like whatever/280/151 (and
>> deal specially with the revisions < 1000 where it would use whatever/0/123 ).
> 
> That would be possible.
> 
>> Or it can be a database query.
> 
> I can imagine a simple sqlite file that can be queried.
> Basically all is possible.
> 
> Martin
> 
>>
>>     Jakub
>>
> 

I've got it, we want to use:
http://httpd.apache.org/docs/trunk/rewrite/rewritemap.html#dbm

which allows using a map file with additional index. There's svn-to-git.txt file:
https://drive.google.com/file/d/1xZ7TwvqcV6zErup920OLhb09tePgSJHQ/view?usp=sharing

that should be transformed by:
$ httxt2dbm -i svn-to-git.txt -o svn-to-git.map

Martin

  reply	other threads:[~2020-04-03 13:44 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
2020-04-03  8:54       ` Jakub Jelinek
2020-04-03  9:23         ` Martin Liška
2020-04-03 13:44           ` Martin Liška [this message]
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=b2a001df-820e-1d3d-65b5-89ef2992b1b2@suse.cz \
    --to=mliska@suse.cz \
    --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).