From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Andreas Ericsson <ae@op5.se>
Cc: git@vger.kernel.org
Subject: Re: Errors GITtifying GCC and Binutils
Date: Sat, 25 Mar 2006 11:17:21 +0100 [thread overview]
Message-ID: <20060325101721.GJ31387@lug-owl.de> (raw)
In-Reply-To: <4424443F.5090209@op5.se>
[-- Attachment #1: Type: text/plain, Size: 1052 bytes --]
On Fri, 2006-03-24 20:10:55 +0100, Andreas Ericsson <ae@op5.se> wrote:
> Jan-Benedict Glaw wrote:
> >On Wed, 2006-03-22 14:33:37 +0100, Jan-Benedict Glaw <jbglaw@lug-owl.de>
> >wrote:
> >
> >Since it seems nobody looked at the GCC import run (which means to use
> >the svnimport), I ran it again, under strace control:
>
> If you send me a bzipped tar-ball of the repo you're trying to import,
> preferrably with all the patches to cvsps you've tried, I'll see what I
> can do over the weekend.
It's the regular SVN-based sources of GCC at their upstream location.
In their CVS timeline, they had the repository rsync'able, but I guess
with SVN we only get access through the SVN server.
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O
für einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-03-25 10:17 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
2006-03-23 18:12 ` sean
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
2006-03-23 22:05 ` sean
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 [this message]
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 ` Errors GITtifying GCC and Binutils James Cloos
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=20060325101721.GJ31387@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=ae@op5.se \
--cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.