From: Jeffrey Walton <noloader@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: Please fix the useless email prompts
Date: Sat, 19 Aug 2017 14:02:09 -0400 [thread overview]
Message-ID: <CAH8yC8mpPRN2y1k07_Jk9QP88=gpLKNWfV3W0QQwXTWxyL5STQ@mail.gmail.com> (raw)
In-Reply-To: <xmqqbmnba50e.fsf@gitster.mtv.corp.google.com>
On Sat, Aug 19, 2017 at 12:36 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Jeffrey Walton <noloader@gmail.com> writes:
>
>> Is it possible to fix the issue shown below?
>>
>> I'm on a test machine. All I do is update to the latest code, build
>> the library and run the self tests.
>>
>> The test user account does not have a name and does not have an email
>> address. There's nothing to provide.
>>
>> There's no reason to break my workflows for useless Git policies like
>> "please tell me your email address". Its not my policy, and there's
>> nothing critical about it.
>>
>> ...
> Hasn't this been asked and answered already?
>
> https://public-inbox.org/git/CACBZZX4vEOD-4a-eK-uBxmFrb1GLSvJKxHW51whCSbCZdh7amQ@mail.gmail.com/
Its 2017. I'd like the tools to work for me instead of me working for the tools.
Jeff
next prev parent reply other threads:[~2017-08-19 18:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-19 15:10 Please fix the useless email prompts Jeffrey Walton
2017-08-19 16:36 ` Junio C Hamano
2017-08-19 18:02 ` Jeffrey Walton [this message]
2017-08-19 19:17 ` Patryk Obara
2017-08-20 9:18 ` Jeff King
2017-08-20 10:19 ` Kaartic Sivaraam
2017-08-20 12:40 ` Andrew Ardill
2017-08-20 21:57 ` Anatolii Borodin
2017-08-20 23:32 ` Andrew Ardill
2017-08-20 23:56 ` Junio C Hamano
2017-08-23 15:35 ` Jeff King
2017-08-23 17:36 ` Junio C Hamano
2017-08-20 21:50 ` Anatolii Borodin
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='CAH8yC8mpPRN2y1k07_Jk9QP88=gpLKNWfV3W0QQwXTWxyL5STQ@mail.gmail.com' \
--to=noloader@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.