[llvm-dev] Reminder: SVN will be retired on Oct 21, 2019 -- Please migrate your workflows to github ASAP.

Sam Elliott via llvm-dev llvm-dev at lists.llvm.org
Fri Jul 12 07:34:52 PDT 2019


Tom

I attempted to use `git llvm push` with the test-suite repository (which isn’t moving to the monorepo) and it didn’t work. I presume this was expected.

It is slightly infuriating that most of the documentation as to how to use the SVN repositories has vanished (which is still relevant to contributing to test-suite and lnt), and it seems there is little guidance about what these repos will do when the monorepo moves to git and GitHub. 

More clarity on the situation for these repos, and the tooling that’s expected to be used with them, would be useful.

Sam

> On 12 Jul 2019, at 3:23AM, Tom Stellard via llvm-dev <llvm-dev at lists.llvm.org> wrote:
> 
> Hi,
> 
> We are still on track to retire SVN and complete the transition to GitHub
> by Oct 21, 2019 (This year's US Dev Meeting).
> 
> Even though this 3+ months away, it is very important that you begin to migrate
> your workflows to GitHub as soon as possible.  For developers, this means using
> the git-llvm script to commit changes and for CI systems or other read-only use
> cases can begin fetching code directly from GitHub.
> 
> I have created a migration status page, so you can track the progress of the migration:
> http://llvm.org/GitHubMigrationStatus.html  There is also a link to instructions for
> how to use the git-llvm script for committing changes.
> 
> If you would like to help with any of the TODOs on that page, please comment on the
> bugzilla associated with the task.
> 
> Thanks,
> Tom
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

--
Sam Elliott
Software Developer - LLVM
lowRISC CIC
selliott at lowrisc.org
--







More information about the llvm-dev mailing list