From: Sverre Rabbelier <srabbelier@gmail.com>
To: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Cc: Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>,
Jonathan Niedier <jrnieder@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH] Take it easy on unallowed access to non-existent repository
Date: Sun, 11 Apr 2010 17:45:46 +0200 [thread overview]
Message-ID: <l2ifabb9a1e1004110845l7cc89b70y9878dad9e1537e8d@mail.gmail.com> (raw)
In-Reply-To: <1270983682-12215-1-git-send-email-pclouds@gmail.com>
Heya,
2010/4/11 Nguyễn Thái Ngọc Duy <pclouds@gmail.com>:
> if (startup_info && !startup_info->have_run_setup_gitdir)
> - die("internal error: access to .git/config without repo setup");
> + warning("Broken repository setup: early access to $GIT_DIR/config");
This makes it sound like whatever is the problem is caused by the
repository that is being operated on, rather than git's code, is that
correct?
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2010-04-11 15:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 0:48 What's cooking in git.git (Apr 2010, #03; Wed, 07) Junio C Hamano
2010-04-08 6:05 ` Johannes Sixt
2010-04-08 6:33 ` Junio C Hamano
2010-04-08 9:01 ` Fredrik Kuivinen
2010-04-08 9:14 ` ***SPAM*** " Tor Arntsen
2010-04-08 9:16 ` Tor Arntsen
2010-04-08 7:38 ` Jeff King
2010-04-08 21:42 ` nd/setup Jonathan Nieder
2010-04-09 0:13 ` nd/setup Jeff King
2010-04-11 11:01 ` [PATCH] Take it easy on unallowed access to non-existent repository Nguyễn Thái Ngọc Duy
2010-04-11 15:45 ` Sverre Rabbelier [this message]
2010-04-11 17:49 ` Nguyen Thai Ngoc Duy
2010-04-11 17:52 ` Sverre Rabbelier
2010-04-11 17:57 ` Nguyen Thai Ngoc Duy
2010-04-09 5:46 ` nd/setup Nguyen Thai Ngoc Duy
2010-04-09 5:57 ` nd/setup Jonathan Nieder
2010-04-09 6:56 ` nd/setup Nguyen Thai Ngoc Duy
2010-04-11 17:57 ` nd/setup Nguyen Thai Ngoc Duy
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=l2ifabb9a1e1004110845l7cc89b70y9878dad9e1537e8d@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
/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).