Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 3320256
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 17, 20262026-05-17T22:55:18+00:00 2026-05-17T22:55:18+00:00

Apparently I mistyped my email a long time ago, whenever I was setting up

  • 0

Apparently I mistyped my email a long time ago, whenever I was setting up git, and so my email has been incorrect in many repositories (I typed a 0 instead of an o). I sign all of my commits, so in almost every commit in every repo for years it’s said signed off by: <xxx0@foo.bar> instead of signed off by: <xxxo@foo.bar>. Now I can’t just switch my email, so I would like to switch these commit messages.

I’ve already done the git config --global user.email "xxxo@foo.bar", so this shouldn’t be a problem in the future.

Firstly, is it possible to change the messages on this large of a scale without royally messing things up? I’ve already pushed these changes to multiple servers and others have pulled those changes.

Second, is there a way I could do this quickly in a script? ie:

foreach(commit in log)
{
    change "<xxx0@foo.bar>" to "<xxxo@foo.bar>"
}

All help is appreciated, and thanks!

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-17T22:55:19+00:00Added an answer on May 17, 2026 at 10:55 pm

    If the changesets have already been made public and others have pulled them, then you should not touch them. Modifying them will change their SHAs, which will screw things up for others on a royal scale (see the “Recovering from Upstream Rebase” section on the git rebase page).

    Now that I’ve mentioned that, suppose hypothetically they hadn’t been made public. If that were the case, the tool you’d want to use to modify them all would be git filter-branch.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Apparently my teacher believes that even if we don't have time to learn stuff
Apparently VS 2008 does not allow setting a breakpoint just on the setter of
Apparently using the URL is no good - why is this the case, and
Apparently xrange is faster but I have no idea why it's faster (and no
Apparently we use the Scrum development methodology. Here's generally how it goes: Developers thrash
Apparently there's a lot of variety in opinions out there, ranging from, " Never!
Apparently you can easily obtain a client IP address in WCF 3.5 but not
Apparently, they're confusing. Is that seriously the reason? Can you think of any others?
Apparently I can't move files on different volumes using Directory.Move. I have read that
apparently it works Can you name reasons beyond good practices not to give these

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.