From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
To: "Dom (shymega) Rodriguez" <shymega@shymega.org.uk>,
"git MAILING LIST" <git@vger.kernel.org>
Subject: Re: Rewriting history - email/author change on match?
Date: Tue, 01 Oct 2024 00:22:48 +0200 [thread overview]
Message-ID: <c1cba0df-a8a9-4f33-954e-765a5b2cea8c@app.fastmail.com> (raw)
In-Reply-To: <biapebw5nsonirhirnunsgu4wnbynt4zdn4rud5kdvwljnpz63@3hc3ujx2gosw>
On Tue, Oct 1, 2024, at 00:04, Dom (shymega) Rodriguez wrote:
> Hello,
>
> I've got a few private repos that I am the sole contributor to, but some
> commits are under my usual Git author+email. These commits are
> automated, and I'd like to rewrite commits that match the commit message
> (the message is consistent) and the 'old' author+email to a new
> author+email, but retain the commit message.
>
> The tool that springs to mind is `git-filter-branch`. However, I've also
> come across `git-filter-repo` on GitHub.
>
> I'm a little confused, and I wanted to ask for advice on the list. I did
> try using `git-filter-branch`, but got lost quickly with
> `--commit-filter/`--msg-filter`.
git-filter-repo(1) is better—even `man git-filter-branch` recommends it.
> I also found a 'users' Git mailing list on Google Groups, but by the
> warning I got from Google, it has a spam issue. If this is the wrong
> place to ask for help, please do let me know.
Yes. That place is dead. Avoid it.
Or it was when I looked at it back in February.
https://lore.kernel.org/git/339f17e1-c6a0-4859-aa5b-481dd6e0e91b@app.fastmail.com/
--
Kristoffer Haugsbakk
prev parent reply other threads:[~2024-09-30 22:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 22:04 Rewriting history - email/author change on match? Dom (shymega) Rodriguez
2024-09-30 22:22 ` Kristoffer Haugsbakk [this message]
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=c1cba0df-a8a9-4f33-954e-765a5b2cea8c@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail.com \
--cc=git@vger.kernel.org \
--cc=shymega@shymega.org.uk \
/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).