From: Johannes Sixt <j.sixt@viscovery.net>
To: Tade <yess@hell.org.pl>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Documentation: filter-branch env-filter example
Date: Thu, 14 Feb 2013 07:49:55 +0100 [thread overview]
Message-ID: <511C8913.9090203@viscovery.net> (raw)
In-Reply-To: <511BEDDF.7010800@hell.org.pl>
Am 2/13/2013 20:47, schrieb Tade:
> filter-branch --env-filter example that shows how to change the email address
> in all commits by a certain developer.
> ---
You should sign off your patch. Use a full real name, please.
> 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 ]
This should read
if [ "$GIT_AUTHOR_EMAIL" = john@old.example.com ]
(double quotes, spaces around '='). The paragraph before the example talks
about both author and committer, but the example handles only the author;
it should handle the committer as well.
> + then
> + GIT_AUTHOR_EMAIL=john@new.example.com
> + fi
> + export GIT_AUTHOR_EMAIL
> +' -- --all
> +--------------------------------------------------------
> +
The place where you inserted the example is reasonable, IMO.
> 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
-- Hannes
next prev parent reply other threads:[~2013-02-14 6:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 19:47 [PATCH] Documentation: filter-branch env-filter example Tade
2013-02-14 6:49 ` Johannes Sixt [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-02-14 19:34 Tadeusz Andrzej Kadłubowski
2013-02-14 20:29 ` 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
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=511C8913.9090203@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=yess@hell.org.pl \
/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.
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 NNTP newsgroup(s).