From: "Andrew Arnott" <andrewarnott@gmail.com>
To: git@vger.kernel.org
Subject: Re: How to rewrite author history
Date: Fri, 21 Mar 2008 09:41:14 -0700 [thread overview]
Message-ID: <216e54900803210941i7fe345c2va850fa3ded8eabc8@mail.gmail.com> (raw)
In-Reply-To: <216e54900803210938q4981b5d1t535af419f5b15ad8@mail.gmail.com>
I imported my git repo from an SVN repo, and the authors have
email@SOME-GUID for their email address rather than their actual one
(probably courtesy of Google Code hosting). Rewriting history and
changing all the commit hashes isn't a problem at this point in
development, so how can I do a massive search-and-replace to replace
several specific author emails with the valid ones?
--
Andrew Arnott
next parent reply other threads:[~2008-03-21 16:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <216e54900803210938q4981b5d1t535af419f5b15ad8@mail.gmail.com>
2008-03-21 16:41 ` Andrew Arnott [this message]
2008-03-21 18:40 ` How to rewrite author history Dmitry Potapov
2008-03-22 9:29 ` Samuel Tardieu
2008-03-22 13:11 ` Andrew Arnott
2008-03-22 16:57 ` Jeff King
2008-03-22 19:06 ` Andrew Arnott
2008-03-23 7:09 ` Jeff King
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=216e54900803210941i7fe345c2va850fa3ded8eabc8@mail.gmail.com \
--to=andrewarnott@gmail.com \
--cc=git@vger.kernel.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.
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).