subversion status on gcc.gnu.org

subversion status on gcc.gnu.org

[Frank Ch. Eigler]

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.

If you badly need something else subversionish, please let me know.

- FChE

Re: subversion status on gcc.gnu.org

[Peter Bergner]

On 3/20/20 12:37 PM, Frank Ch. Eigler via Gcc wrote:
> 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.
> 
> If you badly need something else subversionish, please let me know.

Thanks for working on this!!!  However, I still see at least one issue
in the following bugzilla entry:

    https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94123#c4

The first two git style links work, but the last one which points
to the SVN revision doesn't.  Is that a bug in the actual url that
bugzilla added or can we handle these too?

Peter

Re: subversion status on gcc.gnu.org

[Frank Ch. Eigler]

Hi -

> Thanks for working on this!!!  However, I still see at least one issue
> in the following bugzilla entry:
> 
>     https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94123#c4
> 
> The first two git style links work, but the last one which points
> to the SVN revision doesn't.  Is that a bug in the actual url that
> bugzilla added or can we handle these too?

We can/do handle the last one too.  httpd mod_rewrite is powerful.

- FChE

Re: subversion status on gcc.gnu.org

[Peter Bergner]

On 3/24/20 12:06 PM, Frank Ch. Eigler wrote:
>> Thanks for working on this!!!  However, I still see at least one issue
>> in the following bugzilla entry:
>>
>>     https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94123#c4
>>
>> The first two git style links work, but the last one which points
>> to the SVN revision doesn't.  Is that a bug in the actual url that
>> bugzilla added or can we handle these too?
> 
> We can/do handle the last one too.  httpd mod_rewrite is powerful.

Works now.  Thanks for fixing!

Peter

Re: subversion status on gcc.gnu.org

[Gerald Pfeifer]

On Fri, 20 Mar 2020, Frank Ch. Eigler via Overseers wrote:
> 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.

That. Is. Cool. :-)

Thank you! 


Should we document this somewhere?  (Our web pages do not appear to
contain "gcc.gnu.org/r", so probably not.)


On a related note, contribute.html has a link to 
https://gcc.gnu.org/viewcvs/gcc/trunk/contrib/check_GNU_style.sh?view=markup
and gcc-4.8/changes.html has a linkto
https://gcc.gnu.org/viewcvs/trunk/libgfortran/libgfortran.h?content-type=text%2Fplain&view=co
which are broken now.  

Do you have an idea how to go about those?  (Happy to make those changes
then.)

Thanks,
Gerald

Re: subversion status on gcc.gnu.org

[Frank Ch. Eigler]

Hi -

> [...]
> On a related note, contribute.html has a link to 
> https://gcc.gnu.org/viewcvs/gcc/trunk/contrib/check_GNU_style.sh?view=markup
> and gcc-4.8/changes.html has a linkto
> https://gcc.gnu.org/viewcvs/trunk/libgfortran/libgfortran.h?content-type=text%2Fplain&view=co
> which are broken now.  

They could be rewritten into gitweb queries too:

https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=contrib/check_GNU_style.sh
https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=libgfortran/libgfortran.h

Care to try writing the necessary httpd mod_rewrite runes?

- FChE

Re: subversion status on gcc.gnu.org

[Martin Liška]

Hi.

The suggested approach expect that the revision belongs to master
branch. Which is not the case for branch commits like:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91601#c11

Link:
https://gcc.gnu.org/viewcvs?rev=275301&root=gcc&view=rev

Thank you,
Martin

Re: subversion status on gcc.gnu.org

[Georg-Johann Lay]

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**

Johann

Re: subversion status on gcc.gnu.org

[Jakub Jelinek]

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

Re: subversion status on gcc.gnu.org

[Martin Liška]

[-- 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 --]

Re: subversion status on gcc.gnu.org

[Jakub Jelinek]

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?  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 ).
Or it can be a database query.

	Jakub

Re: subversion status on gcc.gnu.org

[Martin Liška]

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
> 

Re: subversion status on gcc.gnu.org

[Martin Liška]

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

Re: subversion status on gcc.gnu.org

[Frank Ch. Eigler]

Hi -

> > > 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.

I'll look into fixing the forwarding regexp.

> 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.

I don't think we will require something that elaborate.

- FChE

Re: subversion status on gcc.gnu.org

[Martin Liška]

On 4/3/20 10:19 PM, Frank Ch. Eigler wrote:
> Hi -
> 
>>>> 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.
> 
> I'll look into fixing the forwarding regexp.
> 
>> 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.
> 
> I don't think we will require something that elaborate.

Well, I still believe we want to use the map file. Reason is that
the gitweb redirection can't deal with SVN revision that don't belong
to trunk.

Thanks,
Martin

> 
> - FChE
> 

Re: subversion status on gcc.gnu.org

[Frank Ch. Eigler]

Hi -

Courtesy of a lovely httpd RewriteMap-basd hack courtesy of Martin, we
have all the svn r##### redirects working, and faster than before.

- FChE

Re: subversion status on gcc.gnu.org

[Martin Liška]

On 4/6/20 1:57 AM, Frank Ch. Eigler wrote:
> Hi -
> 
> Courtesy of a lovely httpd RewriteMap-basd hack courtesy of Martin, we
> have all the svn r##### redirects working, and faster than before.

Great. Thank you application of the RewriteMap!

Martin

> 
> - FChE
> 

Re: subversion status on gcc.gnu.org

[Jakub Jelinek]

On Mon, Apr 06, 2020 at 10:09:24AM +0200, Martin Liška wrote:
> On 4/6/20 1:57 AM, Frank Ch. Eigler wrote:
> > Hi -
> > 
> > Courtesy of a lovely httpd RewriteMap-basd hack courtesy of Martin, we
> > have all the svn r##### redirects working, and faster than before.
> 
> Great. Thank you application of the RewriteMap!

E.g. https://gcc.gnu.org/r105377 or https://gcc.gnu.org/r12345
don't work.

	Jakub

Re: subversion status on gcc.gnu.org

[Martin Liška]

On 4/6/20 10:37 AM, Jakub Jelinek wrote:
> On Mon, Apr 06, 2020 at 10:09:24AM +0200, Martin Liška wrote:
>> On 4/6/20 1:57 AM, Frank Ch. Eigler wrote:
>>> Hi -
>>>
>>> Courtesy of a lovely httpd RewriteMap-basd hack courtesy of Martin, we
>>> have all the svn r##### redirects working, and faster than before.
>>
>> Great. Thank you application of the RewriteMap!
> 
> E.g. https://gcc.gnu.org/r105377 or https://gcc.gnu.org/r12345
> don't work.

These look not valid by svn-rev:

$ git svn-rev 105377 | wc -l
0
$ git svn-rev 12345 | wc -l
0

Martin

> 
> 	Jakub
> 

Re: subversion status on gcc.gnu.org

[Jakub Jelinek]

On Mon, Apr 06, 2020 at 10:46:34AM +0200, Martin Liška wrote:
> On 4/6/20 10:37 AM, Jakub Jelinek wrote:
> > On Mon, Apr 06, 2020 at 10:09:24AM +0200, Martin Liška wrote:
> > > On 4/6/20 1:57 AM, Frank Ch. Eigler wrote:
> > > > Hi -
> > > > 
> > > > Courtesy of a lovely httpd RewriteMap-basd hack courtesy of Martin, we
> > > > have all the svn r##### redirects working, and faster than before.
> > > 
> > > Great. Thank you application of the RewriteMap!
> > 
> > E.g. https://gcc.gnu.org/r105377 or https://gcc.gnu.org/r12345
> > don't work.
> 
> These look not valid by svn-rev:
> 
> $ git svn-rev 105377 | wc -l
> 0
> $ git svn-rev 12345 | wc -l
> 0

Dunno about the latter, but the former then looks like a repo conversion
bug:
https://gcc.gnu.org/legacy-ml/gcc-cvs/2005-10/msg01053.html
(that is the first commit to svn after cvs conversion).

	Jakub

Re: subversion status on gcc.gnu.org

[Martin Liška]

On 4/6/20 10:55 AM, Jakub Jelinek wrote:
> On Mon, Apr 06, 2020 at 10:46:34AM +0200, Martin Liška wrote:
>> On 4/6/20 10:37 AM, Jakub Jelinek wrote:
>>> On Mon, Apr 06, 2020 at 10:09:24AM +0200, Martin Liška wrote:
>>>> On 4/6/20 1:57 AM, Frank Ch. Eigler wrote:
>>>>> Hi -
>>>>>
>>>>> Courtesy of a lovely httpd RewriteMap-basd hack courtesy of Martin, we
>>>>> have all the svn r##### redirects working, and faster than before.
>>>>
>>>> Great. Thank you application of the RewriteMap!
>>>
>>> E.g. https://gcc.gnu.org/r105377 or https://gcc.gnu.org/r12345
>>> don't work.
>>
>> These look not valid by svn-rev:
>>
>> $ git svn-rev 105377 | wc -l
>> 0
>> $ git svn-rev 12345 | wc -l
>> 0
> 
> Dunno about the latter, but the former then looks like a repo conversion
> bug:
> https://gcc.gnu.org/legacy-ml/gcc-cvs/2005-10/msg01053.html
> (that is the first commit to svn after cvs conversion).

I hope we can live with that one missing :) The date of the commit seems suspicious:

commit d3e5a995ec5ceb2c474dd52b9d8558265187829a
Author: Daniel Berlin <dberlin@gcc.gnu.org>
Date:   Fri Oct 28 13:21:13 2005 +0000

     SVN was not moved to SVN :)
     
     From-SVN: r105929

while:
r105377 - /trunk/gcc/DATESTAMP
Date: Thu Oct 27 14:59:55 2005

Based on the SVN revision it should live somewhere:

commit 6c06fbce5c77ffbb0be281d22780a919de4877fe
Author: Mark Mitchell <mark@codesourcery.com>
Date:   Thu Oct 13 23:59:57 2005 +0000

     re PR c++/20721 (crossing of a initialization left undetected on goto)
     
             PR c++/20721
             * cp-tree.h (DECL_NONTRIVIALLY_INITIALIZED_P): New macro.
             * decl.c (duplicate_decls): Merge it into new declarations.
             (decl_jump_unsafe): Use it, rather than DECL_INITIAL.
             (cp_finish_decl): Set it, when appropriate.
             PR c++/20721
             * g++.dg/init/goto2.C: New test.
     
     From-SVN: r105380

commit 02f3e085c7ba33279329aae728aaf42dc922add6
Author: Andrew Haley <aph@redhat.com>
Date:   Thu Oct 13 17:36:07 2005 +0000

     re PR java/24251 (BC-compiled interfaces in libgcj can't be called from non-BC code)
     
     2005-10-12  Andrew Haley  <aph@redhat.com>
     
             PR java/24251
             * link.cc (ensure_method_table_complete): Install Miranda methods
             for interfaces too.
     
     From-SVN: r105375

Martin

> 
> 	Jakub
> 

Re: subversion status on gcc.gnu.org

[Andreas Schwab]

On Apr 06 2020, Jakub Jelinek via Gcc wrote:

> On Mon, Apr 06, 2020 at 10:46:34AM +0200, Martin Liška wrote:
>> On 4/6/20 10:37 AM, Jakub Jelinek wrote:
>> > On Mon, Apr 06, 2020 at 10:09:24AM +0200, Martin Liška wrote:
>> > > On 4/6/20 1:57 AM, Frank Ch. Eigler wrote:
>> > > > Hi -
>> > > > 
>> > > > Courtesy of a lovely httpd RewriteMap-basd hack courtesy of Martin, we
>> > > > have all the svn r##### redirects working, and faster than before.
>> > > 
>> > > Great. Thank you application of the RewriteMap!
>> > 
>> > E.g. https://gcc.gnu.org/r105377 or https://gcc.gnu.org/r12345
>> > don't work.
>> 
>> These look not valid by svn-rev:
>> 
>> $ git svn-rev 105377 | wc -l
>> 0
>> $ git svn-rev 12345 | wc -l
>> 0
>
> Dunno about the latter, but the former then looks like a repo conversion
> bug:
> https://gcc.gnu.org/legacy-ml/gcc-cvs/2005-10/msg01053.html
> (that is the first commit to svn after cvs conversion).

This is strange.  Accoding to "svn diff -c 105377
svn://gcc.gnu.org/svn/gcc" this is a revision on
branches/libstdcxx_so_7-branch.  There is also a gap between r105390 and
r105927 on the gcc-cvs archive, where the latter is the first revision
that agrees with the online repository.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."

Re: subversion status on gcc.gnu.org

[Andrew Pinski]

On Mon, Apr 6, 2020 at 2:15 AM Andreas Schwab via Overseers
<overseers@sourceware.org> wrote:
>
> On Apr 06 2020, Jakub Jelinek via Gcc wrote:
>
> > On Mon, Apr 06, 2020 at 10:46:34AM +0200, Martin Liška wrote:
> >> On 4/6/20 10:37 AM, Jakub Jelinek wrote:
> >> > On Mon, Apr 06, 2020 at 10:09:24AM +0200, Martin Liška wrote:
> >> > > On 4/6/20 1:57 AM, Frank Ch. Eigler wrote:
> >> > > > Hi -
> >> > > >
> >> > > > Courtesy of a lovely httpd RewriteMap-basd hack courtesy of Martin, we
> >> > > > have all the svn r##### redirects working, and faster than before.
> >> > >
> >> > > Great. Thank you application of the RewriteMap!
> >> >
> >> > E.g. https://gcc.gnu.org/r105377 or https://gcc.gnu.org/r12345
> >> > don't work.
> >>
> >> These look not valid by svn-rev:
> >>
> >> $ git svn-rev 105377 | wc -l
> >> 0
> >> $ git svn-rev 12345 | wc -l
> >> 0
> >
> > Dunno about the latter, but the former then looks like a repo conversion
> > bug:
> > https://gcc.gnu.org/legacy-ml/gcc-cvs/2005-10/msg01053.html
> > (that is the first commit to svn after cvs conversion).
>
> This is strange.  Accoding to "svn diff -c 105377
> svn://gcc.gnu.org/svn/gcc" this is a revision on
> branches/libstdcxx_so_7-branch.  There is also a gap between r105390 and
> r105927 on the gcc-cvs archive, where the latter is the first revision
> that agrees with the online repository.

From what I can tell is
https://gcc.gnu.org/legacy-ml/gcc-cvs/2005-10/msg01053.html to
https://gcc.gnu.org/legacy-ml/gcc-cvs/2005-10/msg01066.html was done a
testing SVN repo.  The first real commit to the final SVN conversion
was done at https://gcc.gnu.org/legacy-ml/gcc-cvs/2005-10/msg01067.html
BUT the hooks were not converted over by the repo conversion so
https://gcc.gnu.org/legacy-ml/gcc-cvs/2005-10/msg01068.html was the
first real commit; that is

That is r105377 till r105390 was only ever done on a test SVN repo and
r105927 (hooks) was the first commit to SVN after the conversion from
CVS and r105928 was the first commit to SVN  that is visable in GIT
(SVN hooks history did not copy over).

Thanks,
Andrew Pinski
.

>
> Andreas.
>
> --
> Andreas Schwab, schwab@linux-m68k.org
> GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
> "And now for something completely different."

Re: subversion status on gcc.gnu.org

[Joseph Myers]

On Mon, 6 Apr 2020, Andrew Pinski via Gcc wrote:

> That is r105377 till r105390 was only ever done on a test SVN repo and
> r105927 (hooks) was the first commit to SVN after the conversion from

Actually r105926 (creating the hooks directory) was the first commit in 
the real SVN conversion.  But in addition to SVN hooks deliberately not 
being converted to git, commits that only create / remote empty 
directories generally weren't converted, as git doesn't represent empty 
directories so such commits would be empty, and thus not idiomatically 
present at all, in git.

As for the question about r12345 (cvs2svn-generated creation of a tag that 
was deleted shortly after the move from CVS to SVN), it's in git as commit 
229098288e4883d3b78400650e0b4143e12d0a76.  Given a mirror of the full 
repository, refs/deleted/r106023.256/tags/libc-960701 points to that 
commit - it's not a very useful commit, but it's there if you have the 
full repository.  Maybe the RewriteMap was generated based on the 
fetched-by-default parts of the repository and should be regenerated based 
on a mirror clone to get everything converted from an SVN commit to a git 
commit?

-- 
Joseph S. Myers
joseph@codesourcery.com

Re: subversion status on gcc.gnu.org

[Martin Liška]

On 4/6/20 5:04 PM, Joseph Myers wrote:
> On Mon, 6 Apr 2020, Andrew Pinski via Gcc wrote:
> 
>> That is r105377 till r105390 was only ever done on a test SVN repo and
>> r105927 (hooks) was the first commit to SVN after the conversion from
> 
> Actually r105926 (creating the hooks directory) was the first commit in
> the real SVN conversion.  But in addition to SVN hooks deliberately not
> being converted to git, commits that only create / remote empty
> directories generally weren't converted, as git doesn't represent empty
> directories so such commits would be empty, and thus not idiomatically
> present at all, in git.
> 
> As for the question about r12345 (cvs2svn-generated creation of a tag that
> was deleted shortly after the move from CVS to SVN), it's in git as commit
> 229098288e4883d3b78400650e0b4143e12d0a76.

Hi.

You are right, one can really find the git commit:
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=229098288e4883d3b78400650e0b4143e12d0a76

?  Given a mirror of the full
> repository, refs/deleted/r106023.256/tags/libc-960701 points to that
> commit - it's not a very useful commit, but it's there if you have the
> full repository.

Can you please help me how can one clone (or pull) complete content of git repo?

>  Maybe the RewriteMap was generated based on the
> fetched-by-default parts of the repository and should be regenerated based
> on a mirror clone to get everything converted from an SVN commit to a git
> commit?

Yes, it was based on normal git repo one can get from git://gcc.gnu.org/git/gcc.git.

Thanks,
Martin

Re: subversion status on gcc.gnu.org

[Andreas Schwab]

On Apr 07 2020, Martin Liška wrote:

> Can you please help me how can one clone (or pull) complete content of git repo?

Easiest way is to do a mirror clone.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."

Re: subversion status on gcc.gnu.org

[Martin Liška]

On 4/7/20 9:22 AM, Andreas Schwab wrote:
> On Apr 07 2020, Martin Liška wrote:
> 
>> Can you please help me how can one clone (or pull) complete content of git repo?
> 
> Easiest way is to do a mirror clone.

All right, --mirror is a new option to me.

Doing that.
Thanks,
Martin

> 
> Andreas.
> 

Re: subversion status on gcc.gnu.org

[Martin Liška]

On 4/7/20 9:29 AM, Martin Liška wrote:
> On 4/7/20 9:22 AM, Andreas Schwab wrote:
>> On Apr 07 2020, Martin Liška wrote:
>>
>>> Can you please help me how can one clone (or pull) complete content of git repo?
>>
>> Easiest way is to do a mirror clone.
> 
> All right, --mirror is a new option to me.

There's update SVN to GIT map file:
https://drive.google.com/file/d/1DMuFDu476stLdMxKSaDzv4c81rhMAGEI/view?usp=sharing

It increased number of SVN revisions from 227979 to 275662.

@Frank: Can you please update the MapFile with this one?
Thanks,
Martin

> 
> Doing that.
> Thanks,
> Martin
> 
>>
>> Andreas.
>>
> 

Re: subversion status on gcc.gnu.org

[Frank Ch. Eigler]

Hi -

> There's update SVN to GIT map file:
> https://drive.google.com/file/d/1DMuFDu476stLdMxKSaDzv4c81rhMAGEI/view?usp=sharing

Updated.

- FChE

Re: subversion status on gcc.gnu.org

[Martin Liška]

On 4/7/20 4:09 PM, Frank Ch. Eigler wrote:
> Hi -
> 
>> There's update SVN to GIT map file:
>> https://drive.google.com/file/d/1DMuFDu476stLdMxKSaDzv4c81rhMAGEI/view?usp=sharing
> 
> Updated.

Thanks. I can form https://gcc.gnu.org/r12345 works right now.

Martin

> 
> - FChE
>