[llvm-dev] [RFC] One or many git repositories?

Justin Lebar via llvm-dev llvm-dev at lists.llvm.org
Thu Jul 21 17:31:47 PDT 2016

FYI jyknight and I have a hacky script that sort of works for
translating commits to the existing monorepo.  I'm working on cleaning
it up and applying it to David Chisnall's branches.  Hopefully I'll
have something by eod tomorrow.  (This isn't to take a position on
using the existing monorepo as our new source of truth, nor to take a
position on any particular directory layout.)

I wanted to try to merge David's llvm and clang branches into a single
branch -- that would be a big usability improvement over the current
situation.  But there isn't enough information in the repositories to
recover the correct interleaving.  You could try to order by date, but
that only works so long as the history is linear...  So I gave up on
that feature.

I also kind of like the idea of these projected repositories, and if
that's sufficient, awesome, save us some work.

On Thu, Jul 21, 2016 at 5:16 PM, Sanjoy Das via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> Hi Mehdi,
> I really like your idea of having a few "projected" git repositories
> (i.e. capture all commits that touch llvm/ into llvm.git, all that
> touch clang/ to clang.git etc.).  I think it should solve our problem
> of llvm-forks-with-downstream changes very nicely (I think we won't
> have to do anything, as you said).  I still want to sleep on it to see
> if I can spot any issues.
> @David Chisnall and others with local forks: can you spot any
> potential issues with Mehdi's plan?  Are there cases where it won't
> work?
> -- Sanjoy
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

More information about the llvm-dev mailing list