Anton Korobeynikov via llvm-dev
2017-Jun-24 15:56 UTC
[llvm-dev] IMPORTANT: LLVM.org server move on June 24th! (SVN impact)
Hi Chandler,> Worse, all the docs I see say that the git log messages, because the encode > the URL of the SVN server in them, have to be completely rebuilt after > relocating a git-svn repository. This would completely invalidate all of the > git hashes for all of the git mirrors. Several folks have indicated they are > relying on that, including but not limited to the Swift github clones. What > is the plan there?The old URLs will still work. We will double check that everything will be "like before". -- With best regards, Anton Korobeynikov Department of Statistical Modelling, Saint Petersburg State University
Chandler Carruth via llvm-dev
2017-Jun-24 16:57 UTC
[llvm-dev] IMPORTANT: LLVM.org server move on June 24th! (SVN impact)
But now git-svn will be unable to rebuild revisions without switching URL and breaking git hashes. Have folks tried this? What commands should git-svn and hit mirror users use to update? On Sat, Jun 24, 2017, 08:57 Anton Korobeynikov <anton at korobeynikov.info> wrote:> Hi Chandler, > > > Worse, all the docs I see say that the git log messages, because the > encode > > the URL of the SVN server in them, have to be completely rebuilt after > > relocating a git-svn repository. This would completely invalidate all of > the > > git hashes for all of the git mirrors. Several folks have indicated they > are > > relying on that, including but not limited to the Swift github clones. > What > > is the plan there? > The old URLs will still work. We will double check that everything > will be "like before". > > -- > With best regards, Anton Korobeynikov > Department of Statistical Modelling, Saint Petersburg State University >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170624/f41b5a32/attachment.html>
Anton Korobeynikov via llvm-dev
2017-Jun-24 16:58 UTC
[llvm-dev] IMPORTANT: LLVM.org server move on June 24th! (SVN impact)
> But now git-svn will be unable to rebuild revisions without switching URL > and breaking git hashes. Have folks tried this? What commands should git-svn > and hit mirror users use to update?They will use old URLs for the sake of compatibility. -- With best regards, Anton Korobeynikov Department of Statistical Modelling, Saint Petersburg State University
Zachary Turner via llvm-dev
2017-Jun-24 20:22 UTC
[llvm-dev] IMPORTANT: LLVM.org server move on June 24th! (SVN impact)
On Sat, Jun 24, 2017 at 9:57 AM Chandler Carruth <chandlerc at gmail.com> wrote:> But now git-svn will be unable to rebuild revisions without switching URL > and breaking git hashes. Have folks tried this? What commands should > git-svn and hit mirror users use to update? >It's possible I'm off base here, but a couple of things: a) This shouldn't be a problem if you're using git with mono-repo (which we should be actively encouraging git-svn users to migrate to, given that it seems to be agreed upon that this is going to happen in some way or another in the future), since it's not using git-svn. b) IIUC the git-svn url is embedded in the commit message, but only locally, not on the server. So the server should continue to work fine, but if you switch URLs the only thing wrong would be your local git hashes, which would probably have to be rebuilt by running `git svn rebase --force` or something similar. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170624/d6e49882/attachment.html>
Possibly Parallel Threads
- IMPORTANT: LLVM.org server move on June 24th! (SVN impact)
- IMPORTANT: LLVM.org server move on June 24th! (SVN impact)
- IMPORTANT: LLVM.org server move on June 24th! (SVN impact)
- IMPORTANT: LLVM.org server move on June 24th! (SVN impact)
- IMPORTANT: LLVM.org server move complete (SVN impact please read)