From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14831 invoked by alias); 10 Jan 2006 00:12:02 -0000 Received: (qmail 14812 invoked from network); 10 Jan 2006 00:12:00 -0000 Received: from unknown (205.217.158.180) by sourceware.org with QMTP; 10 Jan 2006 00:12:00 -0000 Received: (qmail 30962 invoked by uid 10); 10 Jan 2006 00:12:00 -0000 Received: (qmail 21673 invoked by uid 500); 10 Jan 2006 00:11:51 -0000 To: Daniel Jacobowitz Cc: Jim Blandy , Stan Shebs , Eli Zaretskii , gdb@sources.redhat.com Subject: Re: History before 1999 References: <8f2776cb0601070913q365de93g8d80a4886050cba1@mail.gmail.com> <43C298BF.6070209@apple.com> <8f2776cb0601091233s1a8b1c69q9f185ca0c121b837@mail.gmail.com> <20060109225650.GA5940@nevyn.them.org> From: Ian Lance Taylor Date: Tue, 10 Jan 2006 00:12:00 -0000 In-Reply-To: <20060109225650.GA5940@nevyn.them.org> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-01/txt/msg00072.txt.bz2 Daniel Jacobowitz writes: > On Mon, Jan 09, 2006 at 12:33:20PM -0800, Jim Blandy wrote: > > On 1/9/06, Stan Shebs 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