Re: Protocol to tie Bugzilla entry to Gerrit change

[Jaap Keuter <jaap.keuter () xs4all nl>]

Hi,

For now(*) this is done as per https://wiki.wireshark.org/Development/SubmittingPatches#Writing_a_Good_Commit_Message 
<https://wiki.wireshark.org/Development/SubmittingPatches#Writing_a_Good_Commit_Message>

(*) there’s a Big Move coming to a GitLab instance, this will Change Everything(tm).

Thanks,
Jaap

> On 12 Aug 2020, at 20:05, chuck c <bubbasnmp () gmail com> wrote:
>
> What is protocol to tie a bug entry (https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16771 
> <https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16771>)
> to a Gerrit change (https://code.wireshark.org/review/#/c/31973/ <https://code.wireshark.org/review/#/c/31973/>)?
>
> If only done in Bugzilla, will it languish out there till someone takes an interest?
>
> Or add a comment in Gerrit which I assume sends a note to some or all of the people under Owner, Uploader, Reviews, 
> ....  ?

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe