public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: Andrew STUBBS <andrew.stubbs@st.com>, nickc@redhat.com
Cc: binutils@sourceware.org
Subject: Re: SVN for src (was Re: Binutils 2.18 prep)
Date: Wed, 11 Apr 2007 14:18:00 -0000	[thread overview]
Message-ID: <m37isjhub9.fsf@localhost.localdomain> (raw)
In-Reply-To: <461CB6DF.7050509@st.com>

Andrew STUBBS <andrew.stubbs@st.com> writes:

> I would suggest now that the real problem is how to convert CVS to
> SVN. I haven't even got a clue how that could be done. The GCC project
> managed it, but I imagine that it will take a CVS expert some time to
> get that mammoth process completed.

The gcc conversion, which was done by Daniel Berlin, had two
interesting parts.  The first was that the gcc repository was very
large with a lot of revisions, and the conversion process took more
than two days on a powerful system.  The second was that we wanted to
include older gcc version data from the FSF RCS files which were not
in the CVS repository.  I wrote some hacks to include the RCS revision
history in a copy of the CVS repository before the revision.

I would very much like to do the same thing with the old Cygnus
binutils repository at Red Hat.  The problem is the customer
confidential code in the Cygnus repository.  However, we would only be
interested in the Cygnus repository up to the point when the
sourceware repository was created, in May 1999.  When I was at Cygnus
we always wrote our contracts to say that confidential information
could be released when the customer specified or after three years had
passed.  So, unless they changed that policy after I left in 1998, an
eight year lag should be legally OK.

Nick, could you see if you can get permission to release the
binutils/gdb/newlib/cygwin revision history from the Cygnus repository
up through May, 1999?  If you can, I'll work on incorporating that
revision history into the sourceware repository.

I think that would be very convenient for future development.

Ian

  parent reply	other threads:[~2007-04-11 14:15 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22  2:48 Binutils 2.18 prep Daniel Jacobowitz
2007-03-22 10:06 ` SVN for src (was Re: Binutils 2.18 prep) Andrew STUBBS
2007-03-22 10:45   ` Diego 'Flameeyes' Pettenò
2007-03-22 11:06     ` Andrew STUBBS
2007-03-22 11:23       ` Diego 'Flameeyes' Pettenò
2007-03-22 14:07   ` Paul Brook
2007-03-22 14:20     ` Andrew STUBBS
2007-03-22 14:31     ` Joseph S. Myers
2007-03-22 14:11   ` Bob Rossi
2007-03-22 14:17     ` Daniel Jacobowitz
2007-03-22 15:00   ` Daniel Jacobowitz
2007-03-22 15:28     ` Daniel Jacobowitz
2007-03-22 15:51       ` Andrew STUBBS
2007-03-26 14:59         ` Daniel Jacobowitz
2007-03-26 16:32           ` Andrew STUBBS
2007-04-10 17:25             ` Daniel Jacobowitz
2007-04-11 10:22               ` Andrew STUBBS
2007-04-11 11:06                 ` Daniel Jacobowitz
2007-04-11 13:46                   ` Paul Koning
2007-04-11 14:18                 ` Ian Lance Taylor [this message]
2007-04-11 15:00                   ` Daniel Jacobowitz
2007-04-11 15:23                     ` Ian Lance Taylor
2007-03-22 15:35     ` Andrew STUBBS
2007-03-22 16:48     ` DJ Delorie
2007-03-22 17:08       ` Andrew STUBBS
2007-03-22 18:15         ` DJ Delorie
2007-03-23  9:12           ` Andrew STUBBS
2007-03-26 14:57       ` Daniel Jacobowitz
2007-03-26 15:16         ` Daniel Jacobowitz
2007-07-30 18:09 ` Binutils 2.18 prep Daniel Jacobowitz
2007-07-30 18:14   ` H.J. Lu
2007-08-01 17:57   ` Jim Wilson
2007-08-02  0:08     ` l l
2007-08-06 21:13   ` Daniel Jacobowitz
2007-08-07  8:18     ` Add bfin-*rtems* [was: Binutils 2.18 prep] Ralf Corsepius
2007-08-07  9:33       ` Nick Clifton
2007-08-09 11:45     ` Binutils 2.18 prep Matthias Klose
2007-08-13  0:33       ` Daniel Jacobowitz

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=m37isjhub9.fsf@localhost.localdomain \
    --to=iant@google.com \
    --cc=andrew.stubbs@st.com \
    --cc=binutils@sourceware.org \
    --cc=nickc@redhat.com \
    /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).