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