Gentoo Archives: gentoo-dev

From: hasufell <hasufell@g.o>
To: gentoo-dev@l.g.o, Agostino Sarubbo <ago@g.o>
Subject: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: kde-base/kdepim-icons/
Date: Sun, 09 Aug 2015 18:42:15
On 08/09/2015 08:25 PM, Agostino Sarubbo wrote:
> commit: 3fd6580a947db519cb60a4c2a05ec380ceb681d8 > Author: Agostino Sarubbo <ago <AT> gentoo <DOT> org> > AuthorDate: Sun Aug 9 18:23:44 2015 +0000 > Commit: Agostino Sarubbo <ago <AT> gentoo <DOT> org> > CommitDate: Sun Aug 9 18:23:44 2015 +0000 > URL: > > Stable for amd64, wrt bug #556974 >
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 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.