On Fri, Aug 19, 2011 at 02:23:39PM +0200, Michal Sojka wrote: > > Invoking rebase behind the scenes makes me very nervous. In particular: > > > > 1. There is nothing to indicate to the user that they are rewriting a > > string of commits, which is going to wreak havoc if any of the > > commits have been published elsewhere (either pushed somewhere, or > > even present in another local branch). I.e., rebasing generally > > needs to be a conscious decision of the user. > > I added a warning if the edited commit is contained in a remote branch. > Would you consider this sufficient? It's likely problematic if the commit appears in the history of any other ref, unless they are also planning on rebasing that ref, too (which you can't really know, but it is probably better to warn). -Peff -- 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