llvm dev - Jun 2017 - 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>

While svn seems to work, the current mono-repo
<https://github.com/llvm-project/llvm-project-20170507> does not seem to
be
updating.

Takumi, do you know anything about this?

On Sat, Jun 24, 2017 at 1:22 PM Zachary Turner <zturner at google.com>
wrote:
> 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/20170625/0c13a42a/attachment.html>

I think the scripts that update the monorepo will have to be adjusted
somewhat, not sure what all is required there.

We've verified that git-svn and the main git mirrors are healthy.

On Sat, Jun 24, 2017 at 5:24 PM Zachary Turner <zturner at google.com>
wrote:
> While svn seems to work, the current mono-repo
> <https://github.com/llvm-project/llvm-project-20170507> does not seem
to
> be updating.
>
> Takumi, do you know anything about this?
>
>
> On Sat, Jun 24, 2017 at 1:22 PM Zachary Turner <zturner at
google.com> wrote:
>
>> 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/20170625/2f5f637a/attachment.html>