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

> 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>

On 26 July 2016 at 17:59, Mehdi Amini <mehdi.amini at apple.com>
wrote:
> 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.
Ha! Yes it does! Kind of reverse sub-modules. Now I get it.

However, this would require some scripting, right?

AFAIK, GitHub doesn't support hooks at that level, so we'd either have
to host it somewhere else or use some more convoluted solution, no?

cheers,
--renato

> On Jul 26, 2016, at 10:32 AM, Renato Golin <renato.golin at
linaro.org> wrote:
> 
> On 26 July 2016 at 17:59, Mehdi Amini <mehdi.amini at apple.com>
wrote:
>> 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.
> 
> Ha! Yes it does! Kind of reverse sub-modules. Now I get it.
> 
> However, this would require some scripting, right?
Yes, just like we do when exporting from SVN today I think. 
(The script might be slightly less complex since git is natively handling the
export we’re doing today).
> 
> AFAIK, GitHub doesn't support hooks at that level, so we'd either
have
> to host it somewhere else or use some more convoluted solution, no?
Since it is a deterministic process (even if the update does not happen for an
hour, it can be replayed) in this direction (monorepo -> multiple subrepo
contrary to multiple repo -> monorepo) it can be done asynchronously (i.e.
using a cron or a web hook).

— 
Mehdi