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

> On Jul 26, 2016, at 2:15 AM, Renato Golin via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
> 
> On 26 July 2016 at 10:09, Simon Taylor via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
>> Thus downstream developers can continue to use the read-only view of
the independent projects if that is easier for them; but people hacking on
llvm/clang itself get the benefits of easier checkout, patching, bisection,
atomic commits between projects, etc that come from using a monorepo as the
official repository.
> 
> Would this read-only repositories remain with the synchronous version
> stream?
It is possible to continue adding the equivalent of git-svn-id in the commit
message if it is what you’re referring to.

— 
Mehdi

> I think this was one of the points against pure-git without
> sub-modules and without monolithic repository.
> 
> cheers,
> --renato
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

On 26 July 2016 at 09:36, Mehdi Amini via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> It is possible to continue adding the equivalent of git-svn-id in the
commit message if it is what you’re referring to.
Wouldn't that rely on people installing the correct post-commit (pre?)
hooks locally?

Tim.

On 7/26/16 10:46 AM, Tim Northover via llvm-dev wrote:
> On 26 July 2016 at 09:36, Mehdi Amini via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
>> It is possible to continue adding the equivalent of git-svn-id in the
commit message if it is what you’re referring to.
>
> Wouldn't that rely on people installing the correct post-commit (pre?)
> hooks locally?
This kind of thing could always be added after the fact using git notes, 
and without changing the SHAs.


Jon
>
> Tim.
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-- 
Jon Roelofs
jonathan at codesourcery.com
CodeSourcery / Mentor Embedded

> On Jul 26, 2016, at 9:46 AM, Tim Northover <t.p.northover at
gmail.com> wrote:
> 
> On 26 July 2016 at 09:36, Mehdi Amini via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
>> It is possible to continue adding the equivalent of git-svn-id in the
commit message if it is what you’re referring to.
> 
> Wouldn't that rely on people installing the correct post-commit (pre?)
> hooks locally?
I’ll clarify: with Justin’s monorepo proposal we would have a single repository
with all the llvm-projects inside.
There is a natural cross-project synchronization since we share the repository.

While this repository would be the “source-of-truth” like SVN is today, and be
read-write for developers, we would be able to continue to update the separate
existing read-only repositories (http://llvm.org/git/llvm.git
<http://llvm.org/git/llvm.git> http://llvm.org/git/clang.git
<http://llvm.org/git/clang.git> etc.).

When exporting a commit from the monorepo to one of the read-only repository, it
should be possible to generate a “git-svn-id”-like the same way we’re doing when
exporting from SVN today.

Make sense?

— 
Mehdi

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20160726/24d662de/attachment.html>