Clemens Buchacher <drizzd@xxxxxx> writes: [...] > In order to determine a suitable range automatically, it is a reasonable > heuristic to rebase onto the most recent merge commit. Why not additionally / instead take into account remote-tracking branches for "push" remotes? > It does not > guarantee that published commits are not included -- indeed there is no > way to do that. But, the range is usually large enough to contain the > desired commits. Also, this mechanism works regardless of whether or not > branch tracking has been configured. > > So instead of the above command, one can instead use the following: > > git rebase --fix > > By default, the range is limited to a maximum of 20 commits. This can be > changed by passing a different number to --fix, e.g.: > > git rebase --fix=50 > > Signed-off-by: Clemens Buchacher <drizzd@xxxxxx> Nice idea! -- Jakub Narebski Poland -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html