From: Michael J Gruber <git@drmicha.warpmail.net>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>, Johannes Sixt <j6t@kdbg.org>,
Fritz Anderson <fritza@uchicago.edu>,
git@vger.kernel.org, Daniel Barkalow <barkalow@iabervon.org>
Subject: Re: "fatal: index-pack failed" on git-clone
Date: Thu, 09 Jul 2009 10:42:22 +0200 [thread overview]
Message-ID: <4A55AD6E.8080200@drmicha.warpmail.net> (raw)
In-Reply-To: <20090709063735.GA22544@coredump.intra.peff.net>
Jeff King venit, vidit, dixit 09.07.2009 08:37:
> On Wed, Jul 08, 2009 at 03:48:15PM -0700, Junio C Hamano wrote:
>
>>> However, if Fritz runs 'sudo /usr/local/bin/git clone ...', then the interim
>>> PATH is "/usr/local/bin:/usr/local/libexec/git-core:/bin:/usr/bin" because
>>> this time setup_path() finds a non-empty argv0_path, and the command works.
>>
>> Ahh, that is what I was missing.
>>
>> As I said elsewhere already, I personally do not think sudo is worth
>> supporting compared to the cost of this kind of pain resulting from its
>> misguided "safety" brokenness, but apparently it is widely used. I think
>> what Peff suggests in this thread might be a reasonable workaround.
>
> Yes, I find sudo's restrictions silly, considering that most people use
> it to allow arbitrary code execution, which is why I wrote this some
> time ago:
>
> http://peff.net/tinysu/
>
:)
I think writing "tinysu" is really the best statement one can make about
"sudo"... although "sudoh" would have been the most appropriate name...
Your patch is welcome, of course, and also removes the somewhat
surprising special role played by "git-add".
Michael
next prev parent reply other threads:[~2009-07-09 8:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 15:58 "fatal: index-pack failed" on git-clone Fritz Anderson
2009-07-08 16:42 ` Junio C Hamano
2009-07-08 17:10 ` Fritz Anderson
2009-07-08 17:34 ` Junio C Hamano
2009-07-08 18:22 ` Fritz Anderson
2009-07-08 18:49 ` Junio C Hamano
2009-07-08 19:05 ` Daniel Barkalow
2009-07-08 20:05 ` Fritz Anderson
2009-07-08 20:23 ` Fritz Anderson
2009-07-08 20:42 ` Johannes Sixt
2009-07-08 21:12 ` Jeff King
2009-07-08 21:27 ` Fritz Anderson
2009-07-09 18:11 ` Johannes Sixt
2009-07-08 22:48 ` Junio C Hamano
2009-07-09 6:37 ` Jeff King
2009-07-09 8:42 ` Michael J Gruber [this message]
2009-07-09 23:29 ` A Large Angry SCM
2009-07-13 4:52 ` Jeff King
-- strict thread matches above, loose matches on Subject: below --
2009-07-09 8:06 Johannes Sixt
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=4A55AD6E.8080200@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=barkalow@iabervon.org \
--cc=fritza@uchicago.edu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--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 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.