Re: the gitocalypse repo splitting for v0.3

[Anil Madhavapeddy <anil@xxxxxxxxxx>]

I had a quick go at a sub-tree export by filtering the diff header to look for commit chunks that only touch that file, but it's quite fiddly.

Sounds like it doesn't matter too much to maintain history, and the current repository will be around anyway, as Dave says.

Onwards! I'm about to merge os-bigarray into master (so Haris, dont forget to use the 0.1 tag for your demo in Ottawa).

-anil

On 9 Jun 2012, at 11:09, Richard Mortier wrote:

Can replay each file as a sequence of patches? Would require some (serious) scripting tho- is it worth it?

Or could do the clone, then some of the gc options in git? Never used so not familiar with them... 

Anil Madhavapeddy <anil@xxxxxxxxxx> wrote:

I'm just taking a look at splitting up the Mirage repository for 0.3 and wondered if anyone had a strong opinion on the repository history.  I'm currently doing this:

- Start with mirage.git from master

- 'Git mv' everything into a set of sub-directories which can operate independently.  Each subdir has its own configure/Makefile/ocamlfind script which is copied from a common Makefile structure.

- git subtree export everything into separate repositories to host on github.com/master

The last bit is the unfortunate one, since it filters out changesets before the directory rearrangement and so in practical terms leaves no useful history.  Ideally (somehow), we would keep the individual commit histories on the files even after they've been exported.

One alternative is to clone mirage.git once per component, and delete everything else that isn't needed.  That's a pretty enormous space requirement though.

It's a bit tedious, so I'm inclined to preserve copyrights and the original repository, and reset the history (as I believe xen-api.git did when open-sourced, right Dave?).  Any objections/ideas/agreement?

-anil

This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system: you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.