On 06/03/2015 08:53 PM, Jordan Justen wrote:
> Yet another idea that I've considered is trying to leverage git
> subtree. My idea was that the unified EDK II would remain the main
> upstream.
>
> I would setup an automated process to split each package off using git
> subtree, and push the separate repos.
>...
>
> I never got the time to investigate if git subtree could work as
> required, but this text from the help page seems promising:
>
> "
> split
>
> Extract a new, synthetic project history from the history of the
> <prefix> subtree. The new history includes only the commits
> (including merges) that affected <prefix>, and each of those
> commits now has the contents of <prefix> at the root of the
> project instead of in a subdirectory. Thus, the newly created
> history is suitable for export as a separate git repository.
>
I experimented with git subtree a couple years ago for managing a
project composed of multiple sub-projects. I'm trying to remember what
I thought about it.... It works, but it tends to produce a confusing
git log, IIRC. And if you're going to push to the subtrees, you should
be careful to limit each commit to files in a single (sub)tree. That
requires developer discipline, or a good pre-commit hook.
But for extracting packages into separate read-only repos, it should be
perfect. Note that in that mode, it's very similar (or completely
equivalent?) to "git filter-branch --subdirectory-filter".
--
Brian J. Johnson
--------------------------------------------------------------------
My statements are my own, are not authorized by SGI, and do not
necessarily represent SGI’s positions.
------------------------------------------------------------------------------
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-devel
