git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Alex Riesen <raa.lkml@gmail.com>
To: "Santi Béjar" <sbejar@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] user.default: New config to prevent using the default values for user.*
Date: Fri, 7 Mar 2008 17:41:11 +0100	[thread overview]
Message-ID: <20080307164111.GB4899@steel.home> (raw)
In-Reply-To: <8aa486160803061345k690af0dcv14fe5d62b310ad6f@mail.gmail.com>

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. Others may
be smarter than you.

It could be shortened, thopugh. Maybe remove the asterisks, and
replace "from your system services (gecos)" with a shorter (but
precise) information.


  reply	other threads:[~2008-03-07 16:59 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 [this message]
2008-03-08  0:13       ` Santi Béjar
2008-03-08  1:24         ` Johannes Schindelin
2008-03-08  2:08           ` Junio C Hamano
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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080307164111.GB4899@steel.home \
    --to=raa.lkml@gmail.com \
    --cc=git@vger.kernel.org \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).