[llvm-dev] Status of the git.llvm.org git repos

[Mehdi AMINI via llvm-dev]

Hi,

This was indeed the intended plan (but to update them from the git monorepo
instead of SVN), except that no-one implemented it, and no-one really
requested it as part of the blockers to migrate.
It was also noted a while ago, that if we just write the script to update
these mirror, then anyone can run the script locally from the monorepo and
get the same result, which makes these mirrors not necessary.

This is actually not very complex I think:

cd /tmp/
git clone git at github.com:newren/git-filter-repo.git /tmp/git-filter-repo
git clone git at github.com:llvm/llvm-project.git
cd llvm-project
/tmp/git-filter-repo/git-filter-repo --subdirectory-filter llvm    --force
--refs master
# at this point you have a locally something that looks like
https://git.llvm.org/git/llvm.git ; but the hashes are different.
# the first new commit is 580acd1df4f0c4a865a20ed1e9467425e0dd382e ; we'll
cherry-pick all of them on
# top of the old repo https://git.llvm.org/git/llvm.git
git branch master-rewritten
git remote add llvm https://git.llvm.org/git/llvm.git
git fetch llvm
git reset --hard llvm/master
git cherry-pick
580acd1df4f0c4a865a20ed1e9467425e0dd382e~...master-rewritten --allow-empty
# done! (after a while...)


-- 
Mehdi



On Tue, Feb 25, 2020 at 9:51 AM Tom Honermann via llvm-dev <
llvm-dev at lists.llvm.org> wrote:

> My expectation was that they would continue to be fed from the updates to
> the svn repo.  But again, I don't recall where I got that impression from.
> It may have been a bad assumption on my part.
>
>
>
> Tom.
>
>
>
> *From:* Anton Korobeynikov <anton at korobeynikov.info>
> *Sent:* Tuesday, February 25, 2020 12:36 PM
> *To:* Tom Honermann <thonerma at synopsys.com>
> *Cc:* llvm-dev at lists.llvm.org; Michael Price <mprice at synopsys.com>; Tim
> Prince <trprince at synopsys.com>; Christopher Lapkowski <lapkow at synopsys.com
> >
> *Subject:* Re: [llvm-dev] Status of the git.llvm.org git repos
>
>
>
> Hello
>
> These repos were populated from SVN. Noone worked on migration of them
> to be pulled from monorepo as far as I know.
>
> On Tue, Feb 25, 2020 at 8:28 PM Tom Honermann via llvm-dev
> wrote:
> >
> > I was under the impression that the (non-monorepo) separate LLVM and
> Clang git repos hosted at git.llvm.org would be maintained for a year
> after the transition to the mono repo. I don't recall where I got that
> impression from; probably from some of the many emails on the migration
> topic. I noticed today that updates to these repos ceased on October 22nd
> of last year following transition to the mono repo. Was I simply mistaken
> that these repos were not going to be maintained along with the (read-only)
> svn repo? We had not planned to complete our own transition to the mono
> repo until a little later this year, but if these repos are no longer
> maintained, we'll have to readjust our priorities.
> >
> >
> >
> > I'm aware of the guidance on how to transition (
> https://llvm.org/docs/Proposals/GitHubMove.html#moving-local-branches-to-the-monorepo)
> and am not seeking any advice on how to do so.
> >
> >
> >
> > Tom.
> >
> > _______________________________________________
> > LLVM Developers mailing list
> > llvm-dev at lists.llvm.org
> > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
> --
> With best regards, Anton Korobeynikov
> Department of Statistical Modelling, Saint Petersburg State University
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200229/cb7bb01e/attachment.html>