git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git Rebase blows away GIT_AUTHOR_NAME

From
Jeff King <peff@peff.net>
Date
Jan 12, 2011, 18:21 UTC
Message-ID
<20110112182150.GC31747@sigill.intra.peff.net>
In-Reply-To
<AANLkTinMX0yEPvSc-c=96R42SbFZTjW5Mnveuxk3ZHS=@mail.gmail.com>
On Wed, Jan 12, 2011 at 09:15:41AM -0700, JT Olds wrote:
Show 7 quoted lines
> On every fresh install of Ubuntu that I have used (by default, I use
> ecryptfs for my home directory, which of course has its own set of
> silly Git errors right now), when I clone from a remote repository,
> have changes local to me, and changes on the remote repository, do
> 'git pull --rebase', occasionally my GIT_AUTHOR_NAME gets set to my
> GIT_AUTHOR_EMAIL on my changes that get applied on top of the remote
> changes.
Weird. I have never heard of anything like it.

Some things off the top of my head: Does your GIT_AUTHOR_NAME or GIT_AUTHOR_EMAIL contain any odd characters that might confuse a parser? Do you do anything special with setting up those environment variables in your shell (e.g., in a .bashrc or .profile; those files _shouldn't_ be read by a non-interactive shell, but it's something to investigate)? For that matter, how do you set up your identity in general (by environment, or in ~/.gitconfig, or a local .git/config in each repo), and what does it contain?

Can you try running this in a repo that's giving you problems:
  . git-sh-setup
  git log --format=%H --author=your.name |
  while read rev; do
    get_author_ident_from_commit $rev
    git format-patch -1 --stdout $rev |
      git mailinfo /dev/null /dev/null
  done | less

and check that the output looks sane? I want to make sure there's nothing in your commits that is confusing our parser.

If that doesn't turn up anything, I think the next thing to try would be making a script that reproduces the problem for you, and see if I can reproduce it here.

-Peff
Previous: JT OldsNext: JT Olds
Message 2 of 30 in “Git Rebase blows away GIT_AUTHOR_NAME”
  1. JT OldsJan 12, 2011
  2. Jeff KingJan 12, 2011
  3. JT OldsJan 13, 2011
  4. JT OldsJan 13, 2011
  5. Erik Faye-LundJan 13, 2011
  6. JT OldsJan 13, 2011
  7. Erik Faye-LundJan 13, 2011
  8. Tor ArntsenJan 14, 2011
  9. Erik Faye-LundJan 14, 2011
  10. Tor ArntsenJan 14, 2011
  11. Erik Faye-LundJan 14, 2011
  12. JT OldsJan 14, 2011
  13. Linus TorvaldsJan 14, 2011
  14. Erik Faye-LundJan 14, 2011
  15. Jeff KingJan 14, 2011
  16. Erik Faye-LundJan 14, 2011
  17. Jeff KingJan 14, 2011
  18. Jay SoffianJan 14, 2011
  19. Junio C HamanoJan 14, 2011
  20. Jeff KingJan 14, 2011
  21. Junio C HamanoJan 14, 2011
  22. Jeff KingJan 17, 2011
  23. Erik Faye-LundJan 17, 2011
  24. JT OldsJan 18, 2011
  25. Jay SoffianJan 19, 2011
  26. Tor ArntsenJan 14, 2011
  27. Erik Faye-LundJan 14, 2011
  28. Linus TorvaldsJan 14, 2011
  29. Erik Faye-LundJan 14, 2011
  30. Jeff KingJan 13, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.