On Wed, Apr 17, 2013 at 09:14:54AM -0400, Christopher Covington wrote: > On 04/17/2013 06:29 AM, Jon Medhurst (Tixy) wrote:
> > And with gerrit the patch author needs to get an account enabled with the > > project, produce a git commit against the current tip, > I can't recall ever seeing an upload refused because it wasn't against the > latest commit. What's the error message you get? Or is it possible that you > might be misremembering such an incident? This is a configuration option within gerrit - you can set a repository or branch up to be fast forward only. This is frequently done for kernels as it's relatively easy for a change in one part of the code base to interact with changes in another part (especially board changes interacting with the drivers they instantiate) so the theory is that this will force all the verification to be done with exactly the tree that ends up in gerrit. Obviously there's a tradeoff here with the rebases.
signature.asc
Description: Digital signature
_______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
