From: Marc Weber <marco-oweber@gmx.de>
To: git@vger.kernel.org
Subject: You don't exist, Go away! although user.name has been set
Date: Tue, 16 Sep 2008 03:05:29 +0200 [thread overview]
Message-ID: <20080916010529.GB22597@gmx.de> (raw)
Today I was glad. I 've been able to compile git on a maanged server.
git clone did work as well however running
git fetch <remote location> caused the line
die("You don't exist. Go away!");
to be executed. (the first one)
Before examining that I asked at #git and got the tip to set
user.name and user.email which I did. Then I verified that git
git var GIT_AUTHOR_IDENT and
git var GIT_COMMITTER_IDENT
both printed some values.
I still got the failure above.
I've fixed it for my case by setting
git_default_name and git_default_email just before the check within the
ident.c file (line 76)..
However I want to ask wether I've hit a known problem and wether you
would appreciate me debggung this issue any further?
Maybe I should add that I've been running that git from the build
directory if that matters. The version is 1.6.0 from the official
mirror site.
Marc Weber
next reply other threads:[~2008-09-16 1:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-16 1:05 Marc Weber [this message]
2008-09-16 7:38 ` You don't exist, Go away! although user.name has been set Andreas Ericsson
2008-09-18 11:47 ` Marc Weber
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=20080916010529.GB22597@gmx.de \
--to=marco-oweber@gmx.de \
--cc=git@vger.kernel.org \
/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).