git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "Santi Béjar" <sbejar@gmail.com>,
	"Alex Riesen" <raa.lkml@gmail.com>,
	git@vger.kernel.org
Subject: Re: [PATCH] user.default: New config to prevent using the default values for user.*
Date: Fri, 07 Mar 2008 18:08:22 -0800	[thread overview]
Message-ID: <7v7igeynl5.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LSU.1.00.0803080223030.3975@racer.site> (Johannes Schindelin's message of "Sat, 8 Mar 2008 02:24:29 +0100 (CET)")

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> On Sat, 8 Mar 2008, Santi Béjar wrote:
>
>> On Fri, Mar 7, 2008 at 5:41 PM, Alex Riesen <raa.lkml@gmail.com> wrote:
>> > Santi Béjar, Thu, Mar 06, 2008 22:45:43 +0100:
>> >
>> > > On Wed, Mar 5, 2008 at 9:44 PM, Alex Riesen <raa.lkml@gmail.com> wrote:
>> >  > > Santi Béjar, Wed, Mar 05, 2008 20:18:04 +0100:
>> >  > >
>> >  > >  > @@ -171,7 +171,7 @@ static const char au_env[] = "GIT_AUTHOR_NAME";
>> >  > >  >  static const char co_env[] = "GIT_COMMITTER_NAME";
>> >  > >  >  static const char *env_hint =
>> >  > >  >  "\n"
>> >  > >  > -"*** Your name cannot be determined from your system services (gecos).\n"
>> >  > >  > +"*** Your name cannot be determined.\n"
>> >  > >
>> >  > >  Why not?
>> >  >
>> >  > Is this important? Or in another way, is this useful? The important
>> >  > thing is how you can fix it. But others think otherwise I'll change it
>> >  > to explain the reason.
>> >
>> >  It is precise explanation of what happened. It could be a hint to fix
>> >  gecos field to someone. It is considered useful not to hide
>> >  information, even if you have no idea of how useful it is.

I'd agree with that reasoning on one condition, that is, msysgit folks
would adjust this to whatever gecos equivalent is called in the Windows
world ;-).

I do not personally think this part of the patch is so bad to waste your
brain cells and time arguing about.  I would even suggest removing the
whole "cannot be determined" and just say "Please tell me who you are."

Yes, if you tell people that a lacking GECOS is the underlying reason that
you are getting this message, it would hint them an alternative solution
of talking to their sysadmin to get it fixed, and that one-shot fix will
last for all repositories on that machine (and machines that consult the
same NIS/LDAP for name information).  However, the "config --global"
suggested in that message is also a valid one-shot fix, and hopefully
one-shot across machines that NFS mounts the home directories.  The latter
knowledge can hopefully be reused when you are forced to use git on
Windows, but the fix based on GECOS would probably not.

So I'd even argue that Santi's change to the message is an improvement
that removes geekspeak that is not particularly useful to the end user
in this context.

However, I would also say that this message improvement does not belong to
user.default or whatever the configuration variable is called in this
round of proposal.  It should be a separate patch, and it would be a much
easier sell than the rest of the patch series.


  reply	other threads:[~2008-03-08  2:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-05 19:18 [PATCH] user.default: New config to prevent using the default values for user.* Santi Béjar
2008-03-05 19:54 ` Jon Loeliger
2008-03-05 20:36   ` Santi Béjar
2008-03-05 20:11 ` Johannes Schindelin
2008-03-05 20:21 ` Daniel Barkalow
2008-03-05 20:41   ` Santi Béjar
2008-03-05 20:44 ` Alex Riesen
2008-03-06 21:45   ` Santi Béjar
2008-03-07 16:41     ` Alex Riesen
2008-03-08  0:13       ` Santi Béjar
2008-03-08  1:24         ` Johannes Schindelin
2008-03-08  2:08           ` Junio C Hamano [this message]
2008-03-08  2:22             ` Johannes Schindelin
2008-03-05 21:01 ` Jakub Narebski
2008-03-05 22:35   ` Santi Béjar
2008-03-05 21:29 ` Junio C Hamano
2008-03-05 22:33   ` Santi Béjar
2008-03-05 22:53     ` Junio C Hamano
2008-03-05 23:23       ` Santi Béjar
2008-03-05 23:29         ` Junio C Hamano
2008-03-05 23:39           ` Santi Béjar
2008-03-06  0:29             ` Junio C Hamano
2008-03-06  8:08               ` Santi Béjar

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=7v7igeynl5.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=raa.lkml@gmail.com \
    --cc=sbejar@gmail.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).