Re: git filter-branch re-write history over a range of commits did notwork

From: Philip Oakley <philipoakley@iee.org>
Date: May 28, 2019, 09:33 UTC
Message-ID: <3cf99e80-98aa-639b-ac9d-a882da349fc8@iee.org>
In-Reply-To: <DB7PR05MB5573B5FC17FD1F221F7AAD558D1E0@DB7PR05MB5573.eurprd05.prod.outlook.com>

Hi Chuck,

On 28/05/2019 08:10, LU Chuck wrote: [snip]

Show 12 quoted lines

>> Copying and pasting examples literally is dangerous. You should know what you
>> are doing.
>>
>> "..." is a revision range that computes the mergebase between HEAD and HEAD,
>> which is (surprise!) HEAD, and then includes the two end points, but excludes
>> everything below the mergebase. So, the revision specification that your
>> command ends up with is
>>
>>       HEAD HEAD ^HEAD ^67d9d9 f70bf4
>>
>> Which is empty if f70bf4 is an ancestor of HEAD.
> [LU Chuck] Sorry, I can't understand this part, did you have an documentation about the explanation for ...?

https://git-scm.com/docs/gitrevisions#Documentation/gitrevisions.txt-Theem82308203emthree-dotSymmetricDifferenceNotation

>           "computes the mergebase between HEAD and HEAD" I have no idea about this. And you also talked about mergebase, but in my situation, there is only one branch with 5 commits. I did not have a mergebase.
>           You can check the detail description below.

When there is no specific revisions around the three dots then HEAD is assumed (to save typing)

[snipping the comments on the alternate script]