Wireshark mailing list archives
Re: Submitting a fix to 2.2.4
From: Michael Mann <mmann78 () netscape net>
Date: Fri, 10 Feb 2017 14:58:27 -0500
It would still end up in Gerrit (just like a cherry-pick) Presuming you have a master-2.2 branch (and have pulled the latest): git push ssh://<username>@code.wireshark.org:29418/wireshark HEAD:refs/for/master-2.2 (git review may work, but I've never tried it outside of master branch) -----Original Message----- From: Dario Lombardo <dario.lombardo.ml () gmail com> To: Developer support list for Wireshark <wireshark-dev () wireshark org> Sent: Fri, Feb 10, 2017 2:52 pm Subject: Re: [Wireshark-dev] Submitting a fix to 2.2.4 If the bug was in branch master-2.2 only, what would be the correct way to push a fix in this branch only?
___________________________________________________________________________ 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
Current thread:
- Submitting a fix to 2.2.4 Paul Offord (Feb 10)
- Re: Submitting a fix to 2.2.4 Pascal Quantin (Feb 10)
- Re: Submitting a fix to 2.2.4 Guy Harris (Feb 10)
- Re: Submitting a fix to 2.2.4 Paul Offord (Feb 10)
- Re: Submitting a fix to 2.2.4 Dario Lombardo (Feb 10)
- Re: Submitting a fix to 2.2.4 Michael Mann (Feb 10)
- Re: Submitting a fix to 2.2.4 Guy Harris (Feb 10)
- Re: Submitting a fix to 2.2.4 Jaap Keuter (Feb 11)
- Re: Submitting a fix to 2.2.4 Paul Offord (Feb 10)