Subject: Re: [PATCHv2] Warnings before rebasing -i published history

From: Matthieu Moy <[email-masked]>
Date: Mon, 11 Jun 2012 13:39:13 +0200

[email-masked] writes:

> Matthieu Moy <[email-masked]> a Ã©critÂ :
>
>> Lucien Kong <[email-masked]> writes:
>>
>>> "git rebase -i" can be very dangerous if used on an already published
>>> history. This code detects that one is rewriting a commit that is an
>>> ancestor of a remote-tracking branch, and warns the user through the
>>> editor. This feature is controlled by a new config key
>>> rebase.checkremoterefs.
>>
>> For the lazy, you could provide an example of result in the commit
>> message. People don't want to review how the patch is written if they
>> disagree with the result.
>
> Right, but wouldn't it be better to put the example in the doc
> git-rebase.txt ?

Why not. In any case, it should be easy to find for reviewers (I had to
dig a little to find the expected value in the tests).

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/