public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: binutils@sourceware.org
Subject: Re: svn read of the binutils development repository?
Date: Wed, 12 Apr 2006 06:40:00 -0000	[thread overview]
Message-ID: <20060412060641.GY13324@lug-owl.de> (raw)
In-Reply-To: <20060412043730.GB13022@nevyn.them.org>

[-- Attachment #1: Type: text/plain, Size: 1643 bytes --]

On Wed, 2006-04-12 00:37:30 -0400, Daniel Jacobowitz <drow@false.org> wrote:
> On Wed, Apr 12, 2006 at 09:12:48AM +1000, Ben Elliston wrote:
> > > > Is there any official or unofficial svn interface with the binutils
> > > > development repository available somehow?
> > > 
> > > Not yet.  I've been looking into this, though...
> > 
> > Are there any plans to convert src/ in entirety over to SVN?
> 
> Not yet.
> 
> The major stumbling block is that there is no easy way to check out
> just binutils after a wholesale conversion.

If CVS is abandoned, why would SVN be choosen? For personal use, I'm
using GIT these days and it's a nice experience.

I'm currently running a SVN->GIT conversion for the GCC repo (which is
at aboput 70% of the SVN revision numbers right now) for personal use.
I tried to do that for the Binutils (whole `src'), too, but that
showed up some problems in the CVS import scripts, though these are
worked on.

IBGT on the `check out just binutils' thing: HDDs are somewhat cheap
these days and thus I'd just rule out that argument.

Once the CVS import problems are ironed out, I'd really suggest to
think about GIT.

MfG, JBG
PS: After verifying that at least the tips of all branches are
correct, I'll of course offer the GCC GIT repo for cloning.

-- 
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 --]

  reply	other threads:[~2006-04-12  6:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-09 18:26 Christian Joensson
2006-04-10 15:44 ` Daniel Jacobowitz
2006-04-11 23:57   ` Ben Elliston
2006-04-12  6:06     ` Daniel Jacobowitz
2006-04-12  6:40       ` Jan-Benedict Glaw [this message]
2006-04-12 13:47         ` Paul Brook
2006-04-12 13:55           ` Paul Koning
2006-04-12 13:58             ` Daniel Jacobowitz
2006-04-12 13:58               ` Paul Koning
2006-04-12 15:12                 ` Daniel Jacobowitz
2006-04-12 14:02         ` Daniel Jacobowitz
2006-05-09 14:17 ` Christian Joensson
2006-05-09 14:49   ` Daniel Jacobowitz
2006-08-08 14:31   ` Christian Joensson
2006-08-08 14:52     ` Daniel Jacobowitz
2006-08-08 16:59       ` Daniel Jacobowitz
2006-11-23 11:14     ` Christian Joensson
2006-04-12 13:05 Alessio.MASSARO

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=20060412060641.GY13324@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=binutils@sourceware.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).