Right now, the commit messages used for ebuild & Manifest commits in CVS differ (by repoman signature). However, considering that these two commits are closely bound, I believe that they could be merged into one. And that could happen if the messages were the same. Thus, I'd like to request changing the repoman behavior to use the same commit message for ebuild & Manifest commits.
This is fixed in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=b91eefc82e995ba3463d212f95fa9228c5cf53ae
This is fixed in 2.1.11.25 and 2.2.0_alpha136.
The request leveled here is whacky; the commit messages differing in text is fine (seriously, it is)- if the aesthetics is the complaint, then make the first commit message have the same key in the commit message. Dropping the signing key information however, means that we reverse long term trend, and cvs->git migration no longer can convert that bit of data into a git footer. Keep in mind that for cvs->Git, the complaint about differing messages has no bearing- the manifest double commit doesn't exist in git. Reverse this change please; have both have the same commit message if you like, or differing, but the key needs to be in the commit message.
Reverted: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=8651a9e838e4028e74e115f26e263639c1835173
(In reply to comment #3) > if the aesthetics is the complaint, then make the > first commit message have the same key in the commit message. Okay, done: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=30f3a3fb492bf956d928352037e12d948a8a7a35
This is fixed in 2.1.11.27 and 2.2.0_alpha138.
(In reply to comment #6) > This is fixed in 2.1.11.27 and 2.2.0_alpha138. Sweet; appreciate the turn around time (nothing worse than finding a day to be active on cvs2git, then being blocked) :)
