• News
  • Get Acquainted ▼
    • About
    • Download
    • Blog
  • Get Help ▼
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Issue Tracker
  • Develop ▼
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds
  • Project Host
  • SharkFest
Wireshark-dev: [Wireshark-dev] So how are fixes cherry-picked to release branches?
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Guy Harris <gharris@xxxxxxxxx>
Date: Wed, 2 Sep 2020 01:02:25 -0700
Searching for "cherry" on the Wiki finds these pages:

	https://gitlab.com/wireshark/wireshark/-/wikis/Development/Backporting

	https://gitlab.com/wireshark/wireshark/-/wikis/Development/Workflow

	https://gitlab.com/wireshark/wireshark/-/wikis/Development/SubmittingPatches/Git-Review

all of which contain the name "Gerrit".

We should probably update those to reflect whatever the new procedure is.
  • Follow-Ups:
    • Re: [Wireshark-dev] So how are fixes cherry-picked to release branches?
      • From: Jaap Keuter
  • Prev by Date: Re: [Wireshark-dev] GSoD approved technical writer - community bonding phase
  • Next by Date: Re: [Wireshark-dev] So how are fixes cherry-picked to release branches?
  • Previous by thread: Re: [Wireshark-dev] GSoD approved technical writer - community bonding phase
  • Next by thread: Re: [Wireshark-dev] So how are fixes cherry-picked to release branches?
  • Index(es):
    • Date
    • Thread
Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation Back to top