Referencing bug reports in git (WAS: Re: [gentoo-commits] repo/gentoo:master commit in: sci-libs/opencascade/)

classic Classic list List threaded Threaded
82 messages Options
12345
Reply | Threaded
Open this post in threaded view
|

Re: Summary line (was: Re: Referencing bug reports in git)

Rich Freeman
On Mon, Aug 31, 2015 at 10:53 AM, Alec Warner <[hidden email]> wrote:
>>
>> Mostly, because when I see "A version is bumped" I immediately expect
>> to know which version the bump is to, but have to dig out the diff to
>> find out.
>>
>
> So I thought we used to have scripts that would dig out this information and
> populate them in headers?
>

Rather than embedding info about the content of the commit into the
headers, wouldn't it make sense to just obtain it from git on-demand?
Maybe you want to run git whatchaged instead of git log, or use one of
the bazillion different log pretty formats, or define your own?

--
Rich

Reply | Threaded
Open this post in threaded view
|

Re: Summary line

Michael Orlitzky
On 08/31/2015 01:33 PM, Rich Freeman wrote:

> On Mon, Aug 31, 2015 at 10:53 AM, Alec Warner <[hidden email]> wrote:
>>>
>>> Mostly, because when I see "A version is bumped" I immediately expect
>>> to know which version the bump is to, but have to dig out the diff to
>>> find out.
>>>
>>
>> So I thought we used to have scripts that would dig out this information and
>> populate them in headers?
>>
>
> Rather than embedding info about the content of the commit into the
> headers, wouldn't it make sense to just obtain it from git on-demand?
> Maybe you want to run git whatchaged instead of git log, or use one of
> the bazillion different log pretty formats, or define your own?
>

Yes, `git log --stat` tells me what I want `git log` to tell me.


12345