My favorites | Sign in
Project Home Downloads Wiki Issues Source
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 1931: Gerrit should warn when submitting a commit based on an outdated one
2 people starred this issue and may be notified of changes. Back to list
Status:  New
Owner:  ----


Sign in to add a comment
 
Reported by romain.l...@intersec.com, May 27, 2013
************************************************************
***** NOTE: THIS BUG TRACKER IS FOR GERRIT CODE REVIEW *****
***** DO NOT SUBMIT BUGS FOR CHROME, ANDROID, INTERNAL *****
***** ISSUES WITH YOUR COMPANY'S GERRIT SETUP, ETC.    *****
***** THOSE ISSUE BELONG IN DIFFERENT ISSUE TRACKERS!  *****
************************************************************

Affected Version: 2.5.2

What steps will reproduce the problem?
1. Have a change with two patch-sets.
2. Submit a new change with the patch set 1 of the previous change as parent. 

What is the expected output? What do you see instead?

Gerrit should warn (or even reject the change) about that because the new change depends on an outdated one, and cannot be merged in this state.
Sign in to add a comment

Powered by Google Project Hosting