Sergiu has some experience with this. Maybe he knows some best practices or
ways to preserve full history (including git renames).

Thanks,
Eduard

On Wed, Mar 7, 2012 at 1:00 PM, Thomas Mortagne
<[email protected]>wrote:

> I'm doing some experiment and here is another issue: the common way to
> isolate a subproject history is by using git filter-branch
> --subdirectory-filter which isolate history based on the provided path
> but this obviously is blocked by any modification on this path. In
> practice it mean that no history older than the refactoring made when
> we moved to git will be kept (and sometime even worst if other change
> have been made).
>
> Any other idea to isolate history ?
>
> On Tue, Feb 28, 2012 at 12:17 PM, Thomas Mortagne
> <[email protected]> wrote:
> > Hi devs,
> >
> > Since I plan to move some stuff from platform to commons I would like
> > to know what you think of the history in this case.
> >
> > Pros including history:
> > * can access easily the whole history of a moved file. But sometimes
> > changing packages etc make too much difference for git to see it's
> > actually the same file so you loose it anyway.
> >
> > Cons including history:
> > * double the history which make tools like ohloh indicate wrong
> informations
> > * it's a lot easier to move without history
> >
> > WDYT ?
> >
> > Even if it was looking a bit weird to me at first I'm actually +1 to
> > not move the history in this case.
> >
> > Eduard was proposing to include in the first commit of the new
> > repository the id of the last commit containing the files (basically
> > the id of the parent of the commit deleting the files) in the old
> > repository so that it's easier to find it. I'm +1 for this.
> >
> > --
> > Thomas Mortagne
>
>
>
> --
> Thomas Mortagne
> _______________________________________________
> devs mailing list
> [email protected]
> http://lists.xwiki.org/mailman/listinfo/devs
>
_______________________________________________
devs mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/devs

Reply via email to