On Wed, Apr 24, 2013 at 4:04 PM, Alex Xu <alex_y...@yahoo.ca> wrote: > Seems simple enough, as long as `repoman scan` runs quickly. >
This is the key, because if a commit happens anywhere in your process, your push will fail. At first I thought you were suggesting a server-side hook. This essentially has the same problem, though. Manually running repoman may be the cleanest solution. By all means people are welcome to use hooks if they're afraid they'll forget. However, if you run repoman and it is fine, then you just need to repeat pull/rebase, push until you get though. Sure, there is a slight risk something might get missed, but that risk is lower than it is with cvs currently (since the git pull before your repoman check updated the entire repository, and not just the current directory - I doubt anybody does a cvs update on the whole repository before every change as it is so much more expensive). I think our policy should emphasize the what over the how. The what is we want commits that are free from stupid mistakes. The how is repoman. We'll offer suggested workflows, and then it is up to the committer to be responsible. Rich
