public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: Joseph Myers <joseph@codesourcery.com>,
	Andrew Pinski <pinskia@gmail.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
	Jakub Jelinek via Gcc <gcc@gcc.gnu.org>,
	Overseers mailing list <overseers@sourceware.org>,
	Andreas Schwab <schwab@linux-m68k.org>
Subject: Re: subversion status on gcc.gnu.org
Date: Tue, 7 Apr 2020 09:13:42 +0200	[thread overview]
Message-ID: <2fdb9983-5ce0-078b-ac42-e35d41b54351@suse.cz> (raw)
In-Reply-To: <alpine.DEB.2.21.2004061454430.8219@digraph.polyomino.org.uk>

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


  reply	other threads:[~2020-04-07  7:13 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
2020-04-06 15:04                         ` Joseph Myers
2020-04-07  7:13                           ` Martin Liška [this message]
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=2fdb9983-5ce0-078b-ac42-e35d41b54351@suse.cz \
    --to=mliska@suse.cz \
    --cc=gcc@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=overseers@sourceware.org \
    --cc=pinskia@gmail.com \
    --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).