Home page logo

wireshark logo Wireshark mailing list archives

Re: GIT tutorials
From: Evan Huus <eapache () gmail com>
Date: Tue, 11 Mar 2014 20:08:13 -0400

On Tue, Mar 11, 2014 at 7:12 PM, Hadriel Kaplan
<hadriel.kaplan () oracle com> wrote:

On Mar 11, 2014, at 6:42 PM, Gerald Combs <gerald () wireshark org> wrote:

Would `git describe` suit your needs?

$ git describe

The current tag is v1.11.3-rc1. There are 1917 commits between
v1.11.3-rc1 and gd3b8084.

$ git describe --match v1.11.0-rc1

There have been 5874 commits since v1.11.0-rc1 was tagged.


Any way we could have the "v1.11.0-rc1-1917" portion automatically put into the gerrit review once it's been 
cherry-picked into master/master-x.x?

Like if a script is currently generating the "Change has been successfully cherry-picked as ..." message, then have 
it append the 'git describe' output to that message?


I don't understand how that would help end-users? They don't get the
full commit message, just the SHA...
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe

  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]