git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 2/2] ident: make the useConfigOnly error messages more informative

From
Marios Titas <redneb@gmx.com>
Date
Mar 30, 2016, 23:25 UTC
Message-ID
<20160330232552.GA31861@zeno>
In-Reply-To
<xmqqlh4zr492.fsf@gitster.mtv.corp.google.com>
On Wed, Mar 30, 2016 at 03:27:05PM -0700, Junio C Hamano wrote:
Show 22 quoted lines
>Marios Titas <redneb@gmx.com> writes:
>
>> -			    && !(ident_config_given & IDENT_NAME_GIVEN))
>> -				die("user.useConfigOnly set but no name given");
>> +			    && !(ident_config_given & IDENT_NAME_GIVEN)) {
>> +				fputs(env_hint, stderr);
>> +				die("no name was given and auto-detection is disabled
>
>Hmph.  I do not think that this is making the message "more
>informative".
>
>When a user hits this error, the old message allowed the user to
>easily see how to toggle the "disable auto-detection" bit off to let
>the code continue by telling the name of the configuration, but the
>updated message hides that name, making it harder for the user to
>disable the disabling of auto-detection.
>
>I can buy the argument that this change helps the user by making the
>message "less" informative, though.  By discouraging the users from
>toggling the user.useConfigOnly bit off, it indirectly makes the
>other option to work around this error condition, i.e. giving a name
>more explicitly, more appetizing.

Yeah, maybe informative is not the right word. What I meant is that it directs the user to do the "git config user.name" thing, which is likely the most appropriate course of action in this situation. In any event, I think printing the env_hint message would be really helpful in this case.

Previous: Junio C HamanoNext: Junio C Hamano
Message 4 of 10 in “ident: check for useConfigOnly before auto-detection of name/email”
  1. 1/2 ident: check for useConfigOnly before auto-detection of name/emailMarios Titas, Mar 30, 2016
  2. 2/2 ident: make the useConfigOnly error messages more informativeMarios Titas, Mar 30, 2016
  3. Junio C HamanoMar 30, 2016
  4. Marios TitasMar 30, 2016
  5. Junio C HamanoApr 1, 2016
  6. Junio C HamanoApr 12, 2016
  7. Jeff KingMar 31, 2016
  8. Marios TitasMar 31, 2016
  9. Jeff KingMar 31, 2016
  10. Junio C HamanoApr 1, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.