All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeffrey Walton <noloader@gmail.com>
Cc: Davide Fiorentino <davide.fiorentino@gmail.com>,
	Git List <git@vger.kernel.org>
Subject: Re: How to avoid "Please tell me who you are..."?
Date: Wed, 07 Jun 2017 07:32:46 +0900	[thread overview]
Message-ID: <xmqqefuw927l.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAH8yC8k9pJHLuzWneb4aRAEF2zOTCVO_5YJxrCpw28x8bDox0A@mail.gmail.com> (Jeffrey Walton's message of "Fri, 2 Jun 2017 02:37:40 -0400")

Jeffrey Walton <noloader@gmail.com> writes:

> On Fri, Jun 2, 2017 at 2:30 AM, Davide Fiorentino
> <davide.fiorentino@gmail.com> wrote:
>> Is there a reason why you don't want or can't set those details?
>
> Well, they don't exist so there's nothing to set.
>
> The machine below its a CubieBoard used for testing. I remote into it
> with test@. As a matter of policy, no check-ins occur on it. Other
> than the password database and authroized_keys file, there is no
> information on it to be lost or stolen.

One thing I forgot to ask you.  Are you reporting "I have used this
exact procedure to set up a test machine in the past and did not
have this problem, but with newer Git I get this message and cannot
cherry-pick or tag or do anything"?  Or is this something you
noticed with a version of Git you happened to have?

I am trying to make sure this is not reporting a regression, as I am
not aware of any recent change that wanted to make the "unconfigured
user" detection stricter than before.

Thanks.


  reply	other threads:[~2017-06-06 22:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-02  6:02 How to avoid "Please tell me who you are..."? Jeffrey Walton
     [not found] ` <532E194B-3A76-4416-A652-4B1DCE78AB8A@gmail.com>
2017-06-02  6:37   ` Jeffrey Walton
2017-06-06 22:32     ` Junio C Hamano [this message]
2017-06-02  7:00 ` Konstantin Khomoutov
2017-06-02  7:07   ` Jeffrey Walton
2017-06-02  7:15     ` Junio C Hamano
2017-06-02  7:38       ` Ævar Arnfjörð Bjarmason
2017-06-02 23:50         ` Junio C Hamano

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=xmqqefuw927l.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=davide.fiorentino@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=noloader@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 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.