| 1 |
On Sun, Aug 9, 2015 at 2:38 PM, Andrew Savchenko <bircoph@g.o> wrote: |
| 2 |
> On Sun, 9 Aug 2015 20:42:00 +0200 hasufell wrote: |
| 3 |
>> On 08/09/2015 08:25 PM, Agostino Sarubbo wrote: |
| 4 |
>> > commit: 3fd6580a947db519cb60a4c2a05ec380ceb681d8 |
| 5 |
>> > Author: Agostino Sarubbo <ago <AT> gentoo <DOT> org> |
| 6 |
>> > AuthorDate: Sun Aug 9 18:23:44 2015 +0000 |
| 7 |
>> > Commit: Agostino Sarubbo <ago <AT> gentoo <DOT> org> |
| 8 |
>> > CommitDate: Sun Aug 9 18:23:44 2015 +0000 |
| 9 |
>> > URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3fd6580a |
| 10 |
>> > |
| 11 |
>> > Stable for amd64, wrt bug #556974 |
| 12 |
>> > |
| 13 |
>> |
| 14 |
>> So, now we have 21 commits with the exact same commit message: |
| 15 |
>> ===== |
| 16 |
>> Stable for amd64, wrt bug #556974 |
| 17 |
>> ===== |
| 18 |
> |
| 19 |
> And what is wrong with this? Git allows easily and undoubtedly |
| 20 |
> show relations between each commit and files affected. This is |
| 21 |
> _trivial_. |
| 22 |
> |
| 23 |
> I know, there is a "rule" about '^$cat/$pn:' syntax at present wiki |
| 24 |
> page, but I don't see any strong reasoning behind such rule. |
| 25 |
|
| 26 |
So that git shortlog and tools that consume its output (e.g., cgit) |
| 27 |
will produce useful output. |
Archives