From: "Tadeusz Andrzej Kadłubowski" <yess@hell•org.pl>
To: git@vger•kernel.org
Subject: [PATCH] Documentation: filter-branch env-filter example
Date: Thu, 14 Feb 2013 20:34:11 +0100 [thread overview]
Message-ID: <511D3C33.6070902@hell.org.pl> (raw)
filter-branch --env-filter example that shows how to change the email address
in all commits by a certain developer.
---
Documentation/git-filter-branch.txt | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/Documentation/git-filter-branch.txt b/Documentation/git-filter-branch.txt
index dfd12c9..2664cec 100644
--- a/Documentation/git-filter-branch.txt
+++ b/Documentation/git-filter-branch.txt
@@ -329,6 +329,19 @@ git filter-branch --msg-filter '
' HEAD~10..HEAD
--------------------------------------------------------
+You can modify committer/author personal information using `--env-filter`.
+For example, to update some developer's email address use this command:
+
+--------------------------------------------------------
+git filter-branch --env-filter '
+ if [ $GIT_AUTHOR_EMAIL = john@old•example.com ]
+ then
+ GIT_AUTHOR_EMAIL=john@new•example.com
+ fi
+ export GIT_AUTHOR_EMAIL
+' -- --all
+--------------------------------------------------------
+
To restrict rewriting to only part of the history, specify a revision
range in addition to the new branch name. The new branch name will
point to the top-most revision that a 'git rev-list' of this range
--
1.7.11.7
next reply other threads:[~2013-02-14 19:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 19:34 Tadeusz Andrzej Kadłubowski [this message]
2013-02-14 20:29 ` [PATCH] Documentation: filter-branch env-filter example Junio C Hamano
2013-02-14 21:09 ` Jeff King
2013-02-14 21:24 ` Jeff King
2013-02-14 21:51 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2013-02-13 19:47 Tade
2013-02-14 6:49 ` Johannes Sixt
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=511D3C33.6070902@hell.org.pl \
--to=yess@hell$(echo .)org.pl \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox