git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Cloos <cloos@jhcloos.com>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: git@vger.kernel.org
Subject: Re: Errors GITtifying GCC and Binutils
Date: Sat, 25 Mar 2006 04:10:16 -0500	[thread overview]
Message-ID: <m31wwqritj.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <20060322133337.GU20746@lug-owl.de> (Jan-Benedict Glaw's message of "Wed, 22 Mar 2006 14:33:37 +0100")

Isn't gcc in svn nowadays?

I'd try something like:

rsync://gcc.gnu.org/gcc-svn gcc-svn
git-svnimport -C gcc-git -i -v file:///$(pwd)/gcc-svn

unless you have write access, in which case you may prefer:

mkdir gcc-svn && cd gcc-svn
git-svn init svn+ssh://username@gcc.gnu.org/svn/gcc/trunk
git-svn fetch

-JimC
-- 
James H. Cloos, Jr. <cloos@jhcloos.com>

      parent reply	other threads:[~2006-03-25  9:10 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-22 13:33 Errors GITtifying GCC and Binutils Jan-Benedict Glaw
2006-03-22 23:39 ` Linus Torvalds
2006-03-23  0:12   ` Linus Torvalds
2006-03-23  1:28     ` Linus Torvalds
2006-03-23 20:03       ` Jan-Benedict Glaw
2006-03-23 20:42         ` Linus Torvalds
2006-03-24  0:39         ` Chris Shoemaker
2006-03-24  6:12           ` Keith Packard
2006-03-24  7:52           ` Jan-Benedict Glaw
2006-03-25  0:37             ` Chris Shoemaker
2006-03-23  6:09     ` H. Peter Anvin
2006-03-23 15:45       ` Keith Packard
2006-03-23 16:01         ` Linus Torvalds
     [not found]           ` <20060323131200.02c535b8.seanlkml@sympatico.ca>
2006-03-23 18:12             ` sean
2006-03-23 20:38               ` Linus Torvalds
2006-03-23 20:48                 ` Shawn Pearce
2006-03-23 21:11                   ` Ryan Anderson
2006-03-24  0:15                     ` Junio C Hamano
2006-03-23 23:30                   ` Junio C Hamano
2006-03-24 15:12                     ` Johannes Schindelin
2006-03-24 11:11                   ` Mark Wooding
2006-03-24 11:29                     ` Andreas Ericsson
2006-03-23 21:31                 ` David S. Miller
2006-03-23 21:48                   ` Linus Torvalds
2006-03-23 22:36                   ` Timo Hirvonen
     [not found]                 ` <20060323170515.3612dc61.seanlkml@sympatico.ca>
2006-03-23 22:05                   ` sean
2006-03-24 12:32                 ` Ralf Baechle
2006-03-24 12:59                   ` missing git features (was: Re: Errors GITtifying GCC and Binutils) Andreas Ericsson
2006-03-24 16:44                     ` Carl Worth
2006-03-24 18:55                       ` missing git features Andreas Ericsson
2006-03-23 21:02           ` Errors GITtifying GCC and Binutils Ryan Anderson
2006-03-23 21:39             ` Linus Torvalds
2006-03-23 23:51             ` Junio C Hamano
2006-03-24  0:06               ` Ryan Anderson
2006-03-24  0:34                 ` Junio C Hamano
2006-03-24 12:44   ` Ralf Baechle
2006-03-24 18:25 ` Jan-Benedict Glaw
2006-03-24 19:10   ` Andreas Ericsson
2006-03-25 10:17     ` Jan-Benedict Glaw
2006-03-24 19:35   ` Santi Béjar
2006-03-25  8:25   ` Eric Wong
2006-03-26  2:52     ` [PATCH] contrib/git-svn: stabilize memory usage for big fetches Eric Wong
2006-03-25  9:10 ` James Cloos [this message]

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=m31wwqritj.fsf@lugabout.jhcloos.org \
    --to=cloos@jhcloos.com \
    --cc=git@vger.kernel.org \
    --cc=jbglaw@lug-owl.de \
    /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 NNTP newsgroup(s).