git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: JT Olds <jtolds@xnet5.com>
Cc: git@vger.kernel.org
Subject: Re: Git Rebase blows away GIT_AUTHOR_NAME
Date: Wed, 12 Jan 2011 13:21:50 -0500	[thread overview]
Message-ID: <20110112182150.GC31747@sigill.intra.peff.net> (raw)
In-Reply-To: <AANLkTinMX0yEPvSc-c=96R42SbFZTjW5Mnveuxk3ZHS=@mail.gmail.com>

On Wed, Jan 12, 2011 at 09:15:41AM -0700, JT Olds wrote:

> 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

  reply	other threads:[~2011-01-12 18:22 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-12 16:15 Git Rebase blows away GIT_AUTHOR_NAME JT Olds
2011-01-12 18:21 ` Jeff King [this message]
2011-01-13 17:00   ` JT Olds
2011-01-13 17:11     ` JT Olds
2011-01-13 17:47       ` Erik Faye-Lund
2011-01-13 17:52         ` JT Olds
2011-01-13 18:20           ` Erik Faye-Lund
2011-01-14  8:45             ` Tor Arntsen
2011-01-14  8:56               ` Erik Faye-Lund
2011-01-14  9:24                 ` Tor Arntsen
2011-01-14  9:53                   ` Erik Faye-Lund
2011-01-14 14:51                     ` JT Olds
2011-01-14 15:41                     ` Linus Torvalds
2011-01-14 16:13                       ` Erik Faye-Lund
2011-01-14 16:21                         ` Jeff King
2011-01-14 16:30                           ` Erik Faye-Lund
2011-01-14 16:33                             ` Jeff King
2011-01-14 18:02                               ` Jay Soffian
2011-01-14 18:28                           ` Junio C Hamano
2011-01-14 20:07                             ` Jeff King
2011-01-14 22:30                               ` Junio C Hamano
2011-01-17 22:21                           ` Jeff King
2011-01-17 22:29                             ` Erik Faye-Lund
2011-01-18  3:55                             ` JT Olds
2011-01-19  1:33                             ` Jay Soffian
     [not found]                       ` <AANLkTimZF+r2aNzrXsUuHVZR65N5wpOYLutFgGAGoci_@m ail.gmail.com>
2011-01-14 16:21                         ` Tor Arntsen
2011-01-14 16:26                           ` Erik Faye-Lund
2011-01-14 17:18                           ` Linus Torvalds
2011-01-14  9:55                   ` Erik Faye-Lund
2011-01-13 18:47     ` 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=20110112182150.GC31747@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=jtolds@xnet5.com \
    /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).