On Wed, Sep 17, 2014 at 11:28 AM, hasufell <[email protected]> wrote: > NOTE: you may skip running repoman another time if you have manually > verified that the commits you are missing are totally unrelated to your > work (e.g. only affect a package that is not in the dependency chain of > yours). You can do so via: 'git diff $(git merge-base master > remotes/origin/master) remotes/origin/master'
This seems like a reasonable compromise. 99% of the time this will be the case for single-package commits, and for stuff that is tree-wide everybody should be using care anyway. I don't think I've ever made a single package commit in cvs and run into a collision between the time I updated cvs and the time I finished making my changes and doing a commit. -- Rich
