From: Daniel Jacobowitz <drow@false.org>
To: Jim Blandy <jimb@red-bean.com>
Cc: Stan Shebs <shebs@apple.com>, Eli Zaretskii <eliz@gnu.org>,
gdb@sources.redhat.com
Subject: Re: History before 1999
Date: Mon, 09 Jan 2006 22:56:00 -0000 [thread overview]
Message-ID: <20060109225650.GA5940@nevyn.them.org> (raw)
In-Reply-To: <8f2776cb0601091233s1a8b1c69q9f185ca0c121b837@mail.gmail.com>
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 :-)
I've been thinking on and off about the "modules" problem that I
mentioned the last time the idea came up; I think it's not infeasible.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-01-09 22:56 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 [this message]
2006-01-10 0:12 ` Ian Lance Taylor
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=20060109225650.GA5940@nevyn.them.org \
--to=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