Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@airs.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Jim Blandy <jimb@red-bean.com>, Stan Shebs <shebs@apple.com>,
	  Eli Zaretskii <eliz@gnu.org>,
	gdb@sources.redhat.com
Subject: Re: History before 1999
Date: Tue, 10 Jan 2006 00:12:00 -0000	[thread overview]
Message-ID: <m3psn1rlfc.fsf@gossamer.airs.com> (raw)
In-Reply-To: <20060109225650.GA5940@nevyn.them.org>

Daniel Jacobowitz <drow@false.org> writes:

> On Mon, Jan 09, 2006 at 12:33:20PM -0800, Jim Blandy wrote:
> > On 1/9/06, Stan Shebs <shebs@apple.com> wrote:
> > > In theory, an energetic person could graft old public releases into
> > > the repository, making a sort of synthetic history. Easier in SVN
> > > perhaps?
> > 
> > Insertion of revisions into an existing history, even at the front,
> > isn't something SVN has any special support for.  I think you'd have
> > to dump, edit, and re-load the repository.
> 
> However, Ian has some nice hack for stitching CVS repositories together
> during a CVS->SVN transition - he wrote them to add the old-gcc
> repository to GCC.  I bet we could add the additional history in the
> process of switching to SVN, if there's interest in doing that :-)

Sure, that would work.

Ideally, somebody would go through the Cygnus repository and strip out
the redacted stuff.  Unfortunately that would have to be done by
somebody currently at Red Hat.  The simplest approach would be to just
check out each revision one by one, run redact and/or sanitize, and
check the redacted revision into a new repository.  Unfortunately that
would not be reliable, as some code which should have been redacted
was checked in without appropriate markers.  So somebody would have to
actually look at the revisions and make sure that everything was
properly sanitized.

It is perhaps worth noting that the old Cygnus contracts promised to
keep things secret until permitted, or until three years had passed.
If Red Hat kept that up, then in fact everything in the Cygnus
repository up to 1999 is now safe to reveal.

Ian


      reply	other threads:[~2006-01-10  0:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-07 10:31 Eli Zaretskii
2006-01-07 17:14 ` Jim Blandy
2006-01-07 19:10   ` Eli Zaretskii
2006-01-09 17:10     ` Stan Shebs
2006-01-09 20:33       ` Jim Blandy
2006-01-09 22:56         ` Daniel Jacobowitz
2006-01-10  0:12           ` Ian Lance Taylor [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=m3psn1rlfc.fsf@gossamer.airs.com \
    --to=ian@airs.com \
    --cc=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=jimb@red-bean.com \
    --cc=shebs@apple.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