git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
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 05:42:06 +0000	[thread overview]
Message-ID: <DB7PR05MB5573B5B80C8A9CBE867803D88D1E0@DB7PR05MB5573.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <75618ca1-748d-0761-9108-c7deac63cb53@iee.org>



> -----Original Message-----
> From: Philip Oakley <philipoakley@iee.org>
> Sent: Tuesday, May 28, 2019 4:23 AM
> To: Johannes Sixt <j6t@kdbg.org>; LU Chuck <Chuck.LU@edenred.com>
> 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 27/05/2019 19:21, Johannes Sixt wrote:
> > Am 27.05.19 um 10:01 schrieb LU Chuck:
> >> Hi team,
> >>
> >>      The issue comes from
> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_git-2Dfor-2
> Dwindows_git_issues_2206&d=DwICaQ&c=O17m6UdqOAIZh9XQ8pTl4g&r=VcGe
> IeOZ_8_zlrQNSboenYltfxGNIXN_qG6VpZgXVRk&m=yFm7lAdkRLNMT058SHQUjM
> RFKzJNDFteXlohKpZHVCs&s=Sm1p3Yoy21xK0_zYBZ5ixLo-Fk3GAsXygC3I6hTZKTg
> &e= .
> >>
> >>      I want to re-write history by filter-branch command over a range of
> commits, but the command did not work.
> >>      I have referred to the following three documentation about how to use
> git filter-branch:
> >>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__stackoverflow.com_ques
> tions_15250070_running-2Dfilter-2Dbranch-2Dover-2Da-2Drange-2Dof-2Dcom
> mits&d=DwICaQ&c=O17m6UdqOAIZh9XQ8pTl4g&r=VcGeIeOZ_8_zlrQNSboenYltf
> xGNIXN_qG6VpZgXVRk&m=yFm7lAdkRLNMT058SHQUjMRFKzJNDFteXlohKpZHV
> Cs&s=aYMVqrEjVlsjGZCRbqF3dbPPubv2dtNbGETrEqtO01E&e=
> >>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__stackoverflow.com_ques
> tions_28536980_git-2Dchange-2Dcommit-2Ddate-2Dto-2Dauthor-2Ddate&d=D
> wICaQ&c=O17m6UdqOAIZh9XQ8pTl4g&r=VcGeIeOZ_8_zlrQNSboenYltfxGNIXN_q
> G6VpZgXVRk&m=yFm7lAdkRLNMT058SHQUjMRFKzJNDFteXlohKpZHVCs&s=RvjO
> jOEXUwzYJp-O3jssuNpmyCWW-UOit8rwFrcKWBE&e=
> >>
> >> https://urldefense.proofpoint.com/v2/url?u=https-3A__git-2Dscm.com_do
> >>
> cs_git-2Dfilter-2Dbranch&d=DwICaQ&c=O17m6UdqOAIZh9XQ8pTl4g&r=VcGeIeO
> Z
> >>
> _8_zlrQNSboenYltfxGNIXN_qG6VpZgXVRk&m=yFm7lAdkRLNMT058SHQUjMRFKz
> JNDFt
> >> eXlohKpZHVCs&s=fo6afFNkOm35lefwT8Mq1_LTDW9fJWS7q6dupztiPko&e=
> >>
> >>      You can reproduce the problem by the following steps
> >>      1. clone the repository
> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_chucklu_Lee
> tCode_&d=DwICaQ&c=O17m6UdqOAIZh9XQ8pTl4g&r=VcGeIeOZ_8_zlrQNSboen
> YltfxGNIXN_qG6VpZgXVRk&m=yFm7lAdkRLNMT058SHQUjMRFKzJNDFteXlohKpZ
> HVCs&s=amNC8CYj-9Nay21ax37eGw_c_92lh0Z6_VK7sTgCwXQ&e=
> >>      2. checkout to the temp branch
> >>      3. run the command git filter-branch --env-filter 'export
> >> GIT_COMMITTER_DATE="$GIT_AUTHOR_DATE"' ... 67d9d9..f70bf4
> > Did you not tell us everything because you write ... in this message
> > when you cited the command you used, or do you say that you used ...
> > literally in the command?
> 
> The three dots is provided in the literal EXAMPLES section of the man page. That is
> probably an error, as I think it is meant to be an ellipsis to indicate 'insert other
> options here'.
> 
> Simply remove the three dots ('symmetric diff notation') .
> 
> Not sure what the correct change to the man page should be, but clearly it has
> caused confusion. It also takes a moment to properly realise which commits the
> two dot notation will refer to in the example which may further compound the
> confusion about the three dots.
> 
> Philip
[LU Chuck] Hi Hannes,
         I used ... literally when I cited the command. I write the command with ... directly as the document introduce the usage like that.
         You can check the document https://git-scm.com/docs/git-filter-branch#_examples about the --env-filter section.

         Hi Philip,
         I also tried to execute the command without ..., 
         git filter-branch --env-filter 'export GIT_COMMITTER_DATE="$GIT_AUTHOR_DATE"' 67d9d9..f70bf4
         then I will get another error " You must specify a ref to rewrite."

         Hi team
         I have five commits A,B,C,D,E with commit id as following:
         A(67d9d9)<--B(9c1580)<--C(2eec4d)<--D(a45995)<--E(f70bf4)  
         The commits B,C,D,E 's commiter date and author date are not the same. I want to use filter-branch command to make the commiter date same as the author date.
         I am using the following command to achieve re-write history:
         git filter-branch --env-filter 'export GIT_COMMITTER_DATE="$GIT_AUTHOR_DATE"' ... A..E
         However the command did not work.

> >
> >>      4. You will got the info "Found nothing to rewrite"
> >>
> >>      However, it was supposed to overwrite the history from commit 9c1580
> to commit f70bf4, make the commit date same as date.
> >>      I am not sure if I am using the filter-branch correctly, or if there is a bug in
> git?
> >>
> >>      Anyone can help me? Thanks in advance.
> > -- Hannes


  reply	other threads:[~2019-05-28  5:42 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 [this message]
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
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=DB7PR05MB5573B5B80C8A9CBE867803D88D1E0@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).