Jeffrey Walton <noloa...@gmail.com> writes: > On Fri, Jun 2, 2017 at 2:30 AM, Davide Fiorentino > <davide.fiorent...@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.
