On 04/29/2013 09:28 AM, Christopher Covington wrote:
On 04/28/2013 06:18 AM, Mark Brown wrote:
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.
I'm familiar with a submit- or merge-time option for this. It's not clear to me from your reply whether you're referring to this or an upload- or push-time option.
Ohhh. In talking about Gerrit I assumed a workflow that used code review, but in the case where review is bypassed and one pushes to refs/heads/$branch instead of refs/for/$branch, it makes total sense for the restrictions that are seen from the code review workflow when you hit the "submit" button to applied to pushes/uploads. Sorry for my confusion.
Christopher