From: LU Chuck <Chuck.LU@edenred.com>
To: Philip Oakley <philipoakley@iee.org>, Johannes Sixt <j6t@kdbg.org>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
"chuck.lu@qq.com" <chuck.lu@qq.com>
Subject: RE: git filter-branch re-write history over a range of commits did notwork
Date: Tue, 28 May 2019 09:53:16 +0000 [thread overview]
Message-ID: <DB7PR05MB55736ECF9499B108BD0FB7688D1E0@DB7PR05MB5573.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <3cf99e80-98aa-639b-ac9d-a882da349fc8@iee.org>
> -----Original Message-----
> From: Philip Oakley <philipoakley@iee.org>
> Sent: Tuesday, May 28, 2019 5:34 PM
> To: LU Chuck <Chuck.LU@edenred.com>; Johannes Sixt <j6t@kdbg.org>
> Cc: git@vger.kernel.org; chuck.lu@qq.com
> Subject: Re: git filter-branch re-write history over a range of commits did notwork
>
> 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://urldefense.proofpoint.com/v2/url?u=https-3A__git-2Dscm.com_docs_git
> revisions-23Documentation_gitrevisions.txt-2DTheem82308203emthree-2DdotS
> ymmetricDifferenceNotation&d=DwICaQ&c=O17m6UdqOAIZh9XQ8pTl4g&r=VcG
> eIeOZ_8_zlrQNSboenYltfxGNIXN_qG6VpZgXVRk&m=_rDozHXubCFkEsfhMr2QlaP
> n-h_Khfqa3RG0cNmrSxo&s=qdyaJNy6nkAe-4ufeS4o1NdvgoqQQhZDmDjmjQK9k
> Ro&e=
[LU Chuck] Thanks for your documentation about the explanation. Previously I read another documentation https://git-scm.com/book/en/v2/Git-Tools-Revision-Selection#Commit-Ranges.
It's weird the three dots has two different explanation, maybe there should a place to collect these two explanation for three dots.
> > "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)
[LU Chuck] I got you here, that's why you ask me remove the three dots before, right?
>
> [snipping the comments on the alternate script]
next prev parent reply other threads:[~2019-05-28 9:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 8:01 git filter-branch re-write history over a range of commits did notwork LU Chuck
2019-05-27 18:21 ` Johannes Sixt
2019-05-27 20:22 ` Philip Oakley
2019-05-28 5:42 ` LU Chuck
2019-05-28 6:23 ` Johannes Sixt
2019-05-28 7:10 ` LU Chuck
2019-05-28 9:33 ` Philip Oakley
2019-05-28 9:53 ` LU Chuck [this message]
2019-05-28 9:57 ` Johannes Schindelin
2019-05-28 9:59 ` LU Chuck
2019-05-29 5:15 ` LU Chuck
-- strict thread matches above, loose matches on Subject: below --
2019-05-27 8:11 LU Chuck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DB7PR05MB55736ECF9499B108BD0FB7688D1E0@DB7PR05MB5573.eurprd05.prod.outlook.com \
--to=chuck.lu@edenred.com \
--cc=chuck.lu@qq.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
--cc=philipoakley@iee.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).