On Tue, Apr 23, 2013 at 2:00 PM, Jeroen Roovers <j...@gentoo.org> wrote: > Er, you can't be seriously suggesting we will drop repoman checks with > the migration to git? I don't see how that would benefit anyone. >
Interesting point. One thing to keep in mind with git is that commits don't affect the "central repository." Pushes are what impacts the repository. If I spend six months working on a bunch of coordinated package changes, nobody will see a thing until I push those commits and 500 ebuilds all change atomically (not that I'm suggesting that lack of communication is to be encouraged). A repoman check on a commit may not reflect its impact six months later when it actually hits the main tree. The right time to run repoman is probably right before doing a push, regardless of when any git commits were made. That isn't to say that it can't be run sooner. So, splitting something up into multiple commits can be very lightweight, if repoman is only run before the push. This might create a need to be able to run repoman on more than one package directory, but on less than the entire tree (otherwise you'll end up having to do another pull/rebase before you push anyway). Rich
