git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: "SZEDER Gábor" <szeder@ira.uka.de>
Cc: Junio C Hamano <gitster@pobox.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	git@vger.kernel.org
Subject: Re: Octopus merge: unique (?) to git, but is it useful?
Date: Tue, 3 Jun 2008 20:35:16 -0400	[thread overview]
Message-ID: <20080604003516.GA24232@sigill.intra.peff.net> (raw)
In-Reply-To: <20080603231020.GB6588@neumann>

On Wed, Jun 04, 2008 at 01:10:20AM +0200, SZEDER Gábor wrote:

> Yes, the first hunk fixes the problem (and the second one does not
> introduce any new breakage on my system ;)
> 
> However, I don't really see why the new test failed only at me...

Because you were the only person (so far) whose gecos information wasn't
sufficient for git-commit to work. In Junio's case, the test script
accidentally unset the GIT_COMMITTER_{NAME,EMAIL} variables, which
caused git-commit to fall back on the information in /etc/passwd; it
worked, but it was doing something unintended. On your system, that
information wasn't available, so git-commit just broke.

-Peff

  reply	other threads:[~2008-06-04  0:36 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-03  1:14 Octopus merge: unique (?) to git, but is it useful? Jakub Narebski
2008-06-03  2:05 ` Linus Torvalds
2008-06-03  3:56   ` Junio C Hamano
2008-06-03  5:17     ` Junio C Hamano
2008-06-03  5:28       ` Johannes Schindelin
2008-06-03  5:42         ` Junio C Hamano
2008-06-03  8:31           ` Johannes Schindelin
2008-06-03 10:40       ` SZEDER Gábor
2008-06-03 19:30         ` Junio C Hamano
2008-06-03 20:39           ` SZEDER Gábor
2008-06-03 22:08             ` Junio C Hamano
2008-06-03 23:10               ` SZEDER Gábor
2008-06-04  0:35                 ` Jeff King [this message]
2008-06-04  1:02                 ` Junio C Hamano
2008-06-03 14:40     ` Linus Torvalds
2008-06-03 23:11       ` Miklos Vajna
2008-06-04  0:33         ` Junio C Hamano
2008-06-03  4:29   ` Junio C Hamano
2008-06-03  6:39     ` Jakub Narebski
2008-06-03  7:11       ` Junio C Hamano
2008-06-03  7:32   ` Jakub Narebski
2008-06-03  7:53     ` Junio C Hamano
2008-06-03 19:54     ` Linus Torvalds
2008-06-03 20:27       ` Commit annotations (was:: Octopus merge: unique (?) to git, but is it useful?) Jakub Narebski
2008-06-03 20:33         ` Johannes Schindelin
2008-06-03 23:59           ` Johan Herland
2008-06-03  2:16 ` Octopus merge: unique (?) to git, but is it useful? Daniel Villeneuve
2008-06-03 10:06 ` Matthieu Moy
2008-06-03 11:27   ` Jakub Narebski
2008-06-03 11:53     ` Matthieu Moy

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=20080604003516.GA24232@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=szeder@ira.uka.de \
    --cc=torvalds@linux-foundation.org \
    /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).