Wireshark-dev: Re: [Wireshark-dev] "right" git clone address
From: Evan Huus <eapache@xxxxxxxxx>
Date: Thu, 20 Feb 2014 19:26:53 -0500
On Thu, Feb 20, 2014 at 7:20 PM, Gerald Combs <gerald@xxxxxxxxxxxxx> wrote:
> On 2/20/14 6:21 AM, Bálint Réczey wrote:
>> 2014-02-20 14:36 GMT+01:00 Evan Huus <eapache@xxxxxxxxx>:
>>> On Thu, Feb 20, 2014 at 6:52 AM, Bálint Réczey <balint@xxxxxxxxxxxxxxx> wrote:
>>>> Hi All & Gerald,
>>>>
>>>> 2014-02-01 23:04 GMT+01:00 Evan Huus <eapache@xxxxxxxxx>:
>>>>> On Sat, Feb 1, 2014 at 4:58 PM, Toralf Förster <toralf.foerster@xxxxxx> wrote:
>>>>>> As a "follower" of the wireshark code I'm wondering if
>>>>>> https://code.wireshark.org/review/wireshark or
>>>>>> https://code.wireshark.org/git/wireshark is the right address to build
>>>>>> the latest wireshark from source code.
>>>>>>
>>>>>> (If I understand it correctly this question is similar to "kernel" by
>>>>>> Linus versus "kernel-next" by Stephen Rothwell - right ?)
>>>>>
>>>>> No, https://code.wireshark.org/git/wireshark was a read-only mirror of
>>>>> the subversion repo and should be considered dead (I expect Gerald
>>>>> will remove it at some point).
>>>> I think it would be useful to keep it as a read-only mirror for
>>>> browsing the code easily.
>>>
>>> Why? It will have exactly the same contents as the main repository, so
>>> there will be no difference between browsing one or the other.
>> There are probably many links pointing to
>> https://code.wireshark.org/git/wireshark
>> on the Internet and removing the repository will break them.
>> Keeping it updated is trivial OTOH.
>
> I'd prefer to have as few repositories and repository URLs as possible.
> This would hopefully make things less confusing for developers and is
> one less thing to monitor and maintain on the server side. (On the other
> hand I think there's a compelling argument for mirroring to GitHub,
> especially if we can import pull requests into Gerrit.)
>
> For the time being I've redirected the following URL prefixes to Gerrit:
>
> http://anongit.wireshark.org/git
> http://code.wireshark.org/git
> https://code.wireshark.org/git
>
> I'm able to fetch using a couple of old test repositories here. If
> anything isn't redirecting properly please let me know.
>
>
> (It looks like people are still checking out from
> anonsvn.wireshark.org/wireshark. I'm not sure what to do about that.)

Git allows the server to send back special messages for the client to
display along with success/failure (Gerrit uses this to send you the
URL when you upload a new review). I don't know if SVN has something
similar, but if so we could add the migration message there as well.