From: Philip Oakley Date: Tue, 28 May 2019 09:33:32 GMT Subject: Re: git filter-branch re-write history over a range of commits did notwork Message-ID: <3cf99e80-98aa-639b-ac9d-a882da349fc8@iee.org> In-Reply-To: Hi Chuck, On 28/05/2019 08:10, LU Chuck wrote: [snip] >> 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]