On Wed, Aug 26, 2020 at 9:13 AM Graham Bloice
wrote:
> The "Options" droplist Pascal mentions can be seen on this page:
> https://gitlab.com/wireshark/wireshark/-/commit/847d3949c977a39c3cea15a214af02671ccd21e9?merge_request_iid=26
>
> Let us know if you can't see it John.
>
OK, thanks, I see it
On Wed, 26 Aug 2020 at 15:18, chuck c wrote:
> 1. Is there a global notification for issues?
> 2. Any thoughts on cc: for migrated bugs/issues?
>
> https://www.wireshark.org/lists/
>
> For Masochists
> Wireshark-bugs · RSS
> Bug tracker comments. High volume.
> Subscribe/Unsubscribe/Options
> Loc
1. Is there a global notification for issues?
2. Any thoughts on cc: for migrated bugs/issues?
https://www.wireshark.org/lists/
For Masochists
Wireshark-bugs · RSS
Bug tracker comments. High volume.
Subscribe/Unsubscribe/Options
Local archives (no longer provided after December 31, 2016)
MARC arc
On Wed, 26 Aug 2020 at 14:05, Pascal Quantin wrote:
> Hi John,
>
> Le mer. 26 août 2020 à 14:58, John Thacker a
> écrit :
>
>> The official Gitlab instructions (along with the still being transitioned
>> developer's guide) mention the ability to cherry pick merges from the GUI:
>>
>> https://doc
Hi John,
Le mer. 26 août 2020 à 14:58, John Thacker a écrit :
> The official Gitlab instructions (along with the still being transitioned
> developer's guide) mention the ability to cherry pick merges from the GUI:
>
> https://docs.gitlab.com/ee/user/project/merge_requests/cherry_pick_changes.ht
The official Gitlab instructions (along with the still being transitioned
developer's guide) mention the ability to cherry pick merges from the GUI:
https://docs.gitlab.com/ee/user/project/merge_requests/cherry_pick_changes.html#cherry-picking-a-merge-request
https://www.wireshark.org/docs/wsdg_htm
Peter posted the instructions somewhere for that (either on the main wiki,
or the main project). Have to look it up. Basically you have to remove the
association of your fork with the "old" version, and then reset it.
cheers
Am Di., 25. Aug. 2020 um 23:01 Uhr schrieb Dario Lombardo :
>
>
> On Tu
On Aug 25, 2020, at 11:54 PM, Dario Lombardo wrote:
> Gitlab runs a background javascript jobs that pulls the server for new
> comments on a issue.
That's not it. Having a Wireshark issue open in a Safari window doesn't cause
the CPU issue. Having a docs.gitlab.com page open does.
__
