| 1 |
On Sunday 09 August 2015 20:42:00 hasufell wrote: |
| 2 |
> So, now we have 21 commits with the exact same commit message: |
| 3 |
> ===== |
| 4 |
> Stable for amd64, wrt bug #556974 |
| 5 |
> ===== |
| 6 |
> |
| 7 |
> At that point, it's even debatable to have separate commits. |
| 8 |
> |
| 9 |
> IMO, if you stabilize a huge chunk of ebuilds, you have two possibilities: |
| 10 |
> |
| 11 |
> 1. just make it one giant commit (we don't revert stabilizations |
| 12 |
> anyway)... if it's category-based, start the commit message with |
| 13 |
> ===== |
| 14 |
> kde-base: stable after dev-qt/qtgui bump for ia64 |
| 15 |
> ===== |
| 16 |
> if it is related to a particular package (e.g. a bump of dev-lang/ruby |
| 17 |
> and very closely related packages that span across multiple categories) |
| 18 |
> start it with |
| 19 |
> ===== |
| 20 |
> dev-lang/ruby: stabilize for ia64 including reverse dependencies |
| 21 |
> ===== |
| 22 |
> or somesuch (which is still not very nice, but better) |
| 23 |
> |
| 24 |
> 2. Have a sensical commit message for each saparate commit. E.g., make a |
| 25 |
> local bash hack that automatically prepends "category/pn" to your commit |
| 26 |
> message (I think zlogene has done that already) and hope for bug |
| 27 |
> https://bugs.gentoo.org/show_bug.cgi?id=557148 to get more attention. |
| 28 |
> This is better than mass commits if it can be sensibly automated. |
| 29 |
> |
| 30 |
> |
| 31 |
> Anyway. 21 commits with the same message is really confusing. I can see |
| 32 |
> that arch teams might have the most trouble with commit methods, becasue |
| 33 |
> they have the highest commit rate, but we have to improve this. |
| 34 |
|
| 35 |
Since the repoman commit was done per package, I guess the feature requested |
| 36 |
in bug 557148 should fix this type of issue. |
| 37 |
|
| 38 |
|
| 39 |
-- |
| 40 |
Agostino Sarubbo |
| 41 |
Gentoo Linux Developer |
Archives