[racket-dev] proposal for moving to packages: repository

From: Carl Eastlund (cce at ccs.neu.edu)
Date: Thu May 23 06:49:09 EDT 2013

On Thu, May 23, 2013 at 5:49 AM, Eli Barzilay <eli at barzilay.org> wrote:

> 9 hours ago, Carl Eastlund wrote:
> > I was going to comment on the same thing.  While a naive use of "git
> > filter-branch" might not retain the history, it should be entirely
> > possible to do something a little more intelligent and keep that
> > history.
> Just to be clear, this is exactly what you can't get with
> filter-branch.
> > Essentially each of the new repositories could keep the entire
> > history of the original repository, followed by a massive
> > move/rename, then moving forward with an individual package.
> This can work, but it is unrelated to filter-branch: it's basically
> starting each package repository from a clone of the monolithic repo,
> then move & shuffle things around.
> This seems wrong to me in all kinds of ways -- but if someone wants to
> do this with *their* package (ie, not a package that I need to deal
> with), then it's certainly an option.

It doesn't seem wrong to me.  It's an accurate representation of the
history of the project, which is exactly what git is for retaining.  Where
does the problem come from?  If git filter-branch doesn't maintain the
history we need, it's not the right tool for the job.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.racket-lang.org/dev/archive/attachments/20130523/2b5909be/attachment.html>

Posted on the dev mailing list.