From: Philip Oakley <philipoakley@iee.org>
To: Johannes Sixt <j6t@kdbg.org>, LU Chuck <Chuck.LU@edenred.com>
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: Mon, 27 May 2019 21:22:40 +0100 [thread overview]
Message-ID: <75618ca1-748d-0761-9108-c7deac63cb53@iee.org> (raw)
In-Reply-To: <db2dcf54-8b1c-39b1-579c-425ef158c6a1@kdbg.org>
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://github.com/git-for-windows/git/issues/2206.
>>
>> 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://stackoverflow.com/questions/15250070/running-filter-branch-over-a-range-of-commits
>> https://stackoverflow.com/questions/28536980/git-change-commit-date-to-author-date
>> https://git-scm.com/docs/git-filter-branch
>>
>> You can reproduce the problem by the following steps
>> 1. clone the repository https://github.com/chucklu/LeetCode/
>> 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
>
>> 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
next prev parent reply other threads:[~2019-05-27 20:22 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 [this message]
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
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=75618ca1-748d-0761-9108-c7deac63cb53@iee.org \
--to=philipoakley@iee.org \
--cc=Chuck.LU@edenred.com \
--cc=chuck.lu@qq.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.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).