From: "Santi Béjar" <sbejar@gmail.com>
To: "Alex Riesen" <raa.lkml@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] user.default: New config to prevent using the default values for user.*
Date: Sat, 8 Mar 2008 01:13:18 +0100 [thread overview]
Message-ID: <8aa486160803071613pdacc88fkabc10f52da56ad5d@mail.gmail.com> (raw)
In-Reply-To: <20080307164111.GB4899@steel.home>
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'll wait for others to comment.
> Others may
> be smarter than you.
I don't think this is necessary.
Santi
next prev parent reply other threads:[~2008-03-08 0:14 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8aa486160803071613pdacc88fkabc10f52da56ad5d@mail.gmail.com \
--to=sbejar@gmail.com \
--cc=git@vger.kernel.org \
--cc=raa.lkml@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).