Wireshark-dev: Re: [Wireshark-dev] [Wireshark-users] GitLab migration update
From: Roland Knall <rknall@xxxxxxxxx>
Date: Mon, 24 Aug 2020 09:05:33 +0200

> Am 24.08.2020 um 08:50 schrieb Guy Harris <gharris@xxxxxxxxx>:
> 
> On Aug 23, 2020, at 10:42 PM, Gerald Combs <gerald@xxxxxxxxxxxxx> wrote:
> 
>>> On 8/23/20 9:59 PM, Guy Harris wrote:
>>>> On Aug 23, 2020, at 9:33 PM, Gerald Combs <gerald@xxxxxxxxxxxxx> wrote:
>>> 
>>>> You can still comment on Gerrit changes, but it should otherwise be read-only. SSH access is still enabled for now in order to make it easier to migrate changes. I'll shut it off in the next couple of weeks.
>>> 
>>> Does "it" mean "Gerrit" or "SSH access to Gerrit"?
>> 
>> SSH access. I don't have a definite shutdown date for Gerrit, but it won't be for a while.
> 
> There's some potentially useful historical information there, when trying to research why a change was made.
> 
> Is there a way to convert the Gerrit URLs in the issue database to corresponding commits in the repository?

Two possibilities are here, none of which are automatic: 1. You can extract the change Id from the gerrit url and search within gerrit, or 2. the link to the gerrit change is part of the commit message, so searching git-log should yield results
> 
>>> Where is the link to the issues database from https://gitlab.com/wireshark/wireshark?  GitHub has one on the top-level page for GitHub repositories.
>> 
>> There should be an "Issues" link in the left sidebar. The direct link is https://gitlab.com/wireshark/wireshark/issues.
> 
> It's there, but the GitLab folks are not the best icon designers on the planet.  The icon looks like a coffee cup, or a side view of a mailbox with the door opened up, or whatever.  (And what does a rocket have to do with continuous integration?)
> 
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives:    https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe