llvm dev - Nov 2018 - RFC: Dealing with out of tree changes and the LLVM git monorepo

Justin,

I thought we may provide yet another zipper repo, that contains
individual.git and the monorepo.
I guess it would make easier to interact between your repo and the monorepo.

As guys mentioned, a zipper repo is useful for migration, but I think it
would be hard to live in my daily development.

I will experiment.

Takumi
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20181102/485ab9cd/attachment.html>

Takumi,

NAKAMURA Takumi <geek4civic at gmail.com> writes:
> I thought we may provide yet another zipper repo, that contains
> individual.git and the monorepo. I guess it would make easier to
> interact between your repo and the monorepo.
Thank you for explaining. If I understand correctly, this would mean you
have both the zipper and the (rebuilt from scratch) monorepo, in the
same repository. I think I agree this isn't too useful - it makes things
a lot more complicated for a small benefit.
> As guys mentioned, a zipper repo is useful for migration, but I think it
> would be hard to live in my daily development.
>
> I will experiment.
I hope you find that the zipper repo is actually easy to use for daily
development. The history from the official git mirrors exists without
any change, so migrating and looking at git blame works as well as
ever. You can also do things like bisect along the merge commits quite
easily, by making a bisect script that starts off by checking for a top
level llvm dir, like "[ -d llvm ] || exit 125".

I'm looking forward to hearing what you think.

Thanks,
-- Justin