From: JT Olds <jtolds@xnet5.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: Git Rebase blows away GIT_AUTHOR_NAME
Date: Thu, 13 Jan 2011 10:00:45 -0700 [thread overview]
Message-ID: <AANLkTimanDRHwoqSj7i9sVCZkze1L3Qp-zFYwTwHAOHX@mail.gmail.com> (raw)
In-Reply-To: <20110112182150.GC31747@sigill.intra.peff.net>
> 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?
Nah, from my .git/config
[user]
name = JT
email = jt@instructure.com
> 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)?
Nope, the only place in my entire home directory where those get set
are in my filter-branch script to fix them, which I only run after the
problem manifests itself.
> 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?
I have a global identity in ~/.gitconfig
[user]
name = JT
email = hello@jtolds.com
and then in particular topic branches in their .git/config like before.
> 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
I don't have git-sh-setup, which seems like it should be included in
the git-core package, but it's not. I have git-core
1:1.7.1-1.1ubuntu0.1 installed. Obviously this precludes
get_author_ident_from_commit from working.
> 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.
Alright, I'll see what I can do. Thanks.
next prev parent reply other threads:[~2011-01-13 17:05 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
2011-01-13 17:00 ` JT Olds [this message]
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=AANLkTimanDRHwoqSj7i9sVCZkze1L3Qp-zFYwTwHAOHX@mail.gmail.com \
--to=jtolds@xnet5.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).