From: Andrew Pinski <pinskia@gmail.com>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Jakub Jelinek via Gcc <gcc@gcc.gnu.org>,
Andreas Schwab <schwab@linux-m68k.org>,
Jakub Jelinek <jakub@redhat.com>
Subject: Re: subversion status on gcc.gnu.org
Date: Mon, 6 Apr 2020 02:36:31 -0700 [thread overview]
Message-ID: <CA+=Sn1nY_8H_hw1yD9FV7dB1sU7ybOoTNF4WPkKjKyKxmNQBGg@mail.gmail.com> (raw)
In-Reply-To: <874ktxgel8.fsf@igel.home>
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."
next prev parent reply other threads:[~2020-04-06 9:36 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
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 [this message]
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='CA+=Sn1nY_8H_hw1yD9FV7dB1sU7ybOoTNF4WPkKjKyKxmNQBGg@mail.gmail.com' \
--to=pinskia@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=overseers@sourceware.org \
--cc=schwab@linux-m68k.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).