Wireshark-dev: Re: [Wireshark-dev] GIT tutorials
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Evan Huus <eapache@xxxxxxxxx>
Date: Tue, 11 Mar 2014 20:08:13 -0400
On Tue, Mar 11, 2014 at 7:12 PM, Hadriel Kaplan
<hadriel.kaplan@xxxxxxxxxx> wrote:
>
> On Mar 11, 2014, at 6:42 PM, Gerald Combs <gerald@xxxxxxxxxxxxx> wrote:
>
>> Would `git describe` suit your needs?
>>
>> $ git describe
>> v1.11.3-rc1-1917-gd3b8084
>>
>> 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
>> v1.11.0-rc1-5874-gd3b8084
>>
>> There have been 5874 commits since v1.11.0-rc1 was tagged.
>
> Yup.
>
> 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?
>
> -hadriel

I don't understand how that would help end-users? They don't get the
full commit message, just the SHA...