llvm dev - Nov 2019 - LLVM projects and monorepo.

Hello,

I am trying to access https://git.llvm.org/git/llvm to be able to cherry pick
some of the recent commits I did in the monorepo into our downstream llvm-only
repository.

The host seems defunct, is this part of the move to the monorepo?

I think I can just get the patch and remove the `llvm` on top of the paths, but
that’s not a scalable approach.

Francesco

Francesco Petrogalli via llvm-dev
> 
> I am trying to access https://git.llvm.org/git/llvm to be able to cherry
> pick some of the recent commits I did in the monorepo into our downstream
> llvm-only repository.
> 
> The host seems defunct, is this part of the move to the monorepo?
Yes, the repo is at https://github.com/llvm/llvm-project.git now.
> I think I can just get the patch and remove the `llvm` on top of the
> paths, but that’s not a scalable approach.
We used to use -Xsubtree (I think that's the correct spelling) for
accommodating changes in the directory layout.  That might help.
--paulr

> I think I can just get the patch and remove the `llvm` on top of the paths,
but that’s not a scalable approach.
IIRC, the -p option of 'patch' is exactly for doing this. Would that
simplify your use-case?
> On 14. Nov 2019, at 22:12, Francesco Petrogalli via llvm-dev <llvm-dev
at lists.llvm.org> wrote:
> 
> Hello,
> 
> I am trying to access https://git.llvm.org/git/llvm to be able to cherry
pick some of the recent commits I did in the monorepo into our downstream
llvm-only repository.
> 
> The host seems defunct, is this part of the move to the monorepo?
> 
> I think I can just get the patch and remove the `llvm` on top of the paths,
but that’s not a scalable approach.
> 
> Francesco
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

> On Nov 15, 2019, at 1:52 AM, Alex Denisov <1101.debian at gmail.com>
wrote:
> 
>> I think I can just get the patch and remove the `llvm` on top of the
paths, but that’s not a scalable approach.
> 
> IIRC, the -p option of 'patch' is exactly for doing this. Would
that simplify your use-case?
> 
Yes, for a single patch that would work. If there is a way to do that also when
`git cherry-picking` from monorepo to llvm-only it would be great.

Francesco

>> On 14. Nov 2019, at 22:12, Francesco Petrogalli via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
>> 
>> Hello,
>> 
>> I am trying to access https://git.llvm.org/git/llvm to be able to
cherry pick some of the recent commits I did in the monorepo into our downstream
llvm-only repository.
>> 
>> The host seems defunct, is this part of the move to the monorepo?
>> 
>> I think I can just get the patch and remove the `llvm` on top of the
paths, but that’s not a scalable approach.
>> 
>> Francesco
>> _______________________________________________
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org
>> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>

This what `llvm-mirror` used to do, but it is behind now, as SVN hosts 
are offline as well:

https://github.com/llvm-mirror/llvm

Will Dietz mentioned that he would want to offload maintenance of mirror 
to somebody else eventually:

http://lists.llvm.org/pipermail/llvm-dev/2019-July/133869.html

Mirrors of individual projects have the downside that git hashes would 
not be compatible with the monorepo.

-Petr

On 11/14/19 1:12 PM, Francesco Petrogalli via llvm-dev
wrote:
> Hello,
>
> I am trying to access https://git.llvm.org/git/llvm to be able to cherry
pick some of the recent commits I did in the monorepo into our downstream
llvm-only repository.
>
> The host seems defunct, is this part of the move to the monorepo?
>
> I think I can just get the patch and remove the `llvm` on top of the paths,
but that’s not a scalable approach.
>
> Francesco
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev