From: Chris Shoemaker <c.shoemaker@cox•net>
To: Jan-Benedict Glaw <jbglaw@lug-owl•de>
Cc: Linus Torvalds <torvalds@osdl•org>, git@vger•kernel.org
Subject: Re: Errors GITtifying GCC and Binutils
Date: Thu, 23 Mar 2006 19:39:44 -0500 [thread overview]
Message-ID: <20060324003944.GA28652@pe.Belkin> (raw)
In-Reply-To: <20060323200306.GG31387@lug-owl.de>
On Thu, Mar 23, 2006 at 09:03:06PM +0100, Jan-Benedict Glaw wrote:
> On Wed, 2006-03-22 17:28:23 -0800, Linus Torvalds <torvalds@osdl•org> wrote:
> > On Wed, 22 Mar 2006, Linus Torvalds wrote:
> > > This one-liner to cvsps.c seems to make sure we have an ancestor branch
> > > for that "gdb-4.18-branch" branch, at least according to the cvsps output.
> >
> > The "git cvsimport" is still running, but at least it seems to be happily
> > running further past the point it broke earlier.
>
> I've started it once again, too, with the one-liner added to Debian
> unstable's version of cvsps:
>
> It seems there's a patch like
> http://www.gelato.unsw.edu.au/archives/git/0602/16278.html is missing?
> ...or we need a better cvsps. Shall I add it and try again / try to
> continue, or give up on it for now? Though it would be nice to have
> these two large and important source trees under GIT control :-)
You make want to try the cvsps patch I attached to the email here:
http://www.gelato.unsw.edu.au/archives/git/0511/11812.html
Good luck!
-chris
next prev parent reply other threads:[~2006-03-24 0:39 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 [this message]
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 ` 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=20060324003944.GA28652@pe.Belkin \
--to=c.shoemaker@cox$(echo .)net \
--cc=git@vger$(echo .)kernel.org \
--cc=jbglaw@lug-owl$(echo .)de \
--cc=torvalds@osdl$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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