From: Marco Nelissen <marcone@xs4all.nl>
To: Nanako Shiraishi <nanako3@lavabit.com>
Cc: Alex Riesen <raa.lkml@gmail.com>, git@vger.kernel.org
Subject: Re: running git as root
Date: Sun, 14 Jun 2009 14:40:19 -0700 [thread overview]
Message-ID: <3a3d9e520906141440p720df7c1l6e25b71899daaa7c@mail.gmail.com> (raw)
In-Reply-To: <20090614150851.6117@nanako3.lavabit.com>
On Sat, Jun 13, 2009 at 11:08 PM, Nanako Shiraishi<nanako3@lavabit.com> wrote:
> Quoting Alex Riesen <raa.lkml@gmail.com>:
>
>> 2009/6/13 Marco Nelissen <marcone@xs4all.nl>:
>>> When running as root, git fails a number of test cases that expect it
>>> to fail on read-only repositories (for example 't0004-unwritable.sh').
>>> I was thinking of either changing the code so that it checks
>>> permissions itself when opening files as root, or add a prerequisite
>>> to those test cases so that they are skipped when running as root.
>>
>> There is such a prerequisite already (POSIXPERM), but what caused
>> you to run the _tests_ as root?
>>
>>> What would be the preferred way?
>>
>> Use the prerequisite would sound right when not the
>> strangeness of the idea.
>
> I think somebody needs to repost an old patch from the archive.
>
> http://thread.gmane.org/gmane.comp.version-control.git/116729/focus=118385
That's almost identical to the patch I wanted to submit, except for
the name 'SANITY', which doesn't make much sense I think.
prev parent reply other threads:[~2009-06-14 21:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-13 15:25 running git as root Marco Nelissen
2009-06-13 15:42 ` Michael J Gruber
2009-06-14 1:42 ` Marco Nelissen
2009-06-13 17:49 ` Alex Riesen
2009-06-14 1:41 ` Marco Nelissen
2009-06-14 6:08 ` Nanako Shiraishi
2009-06-14 21:40 ` Marco Nelissen [this message]
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=3a3d9e520906141440p720df7c1l6e25b71899daaa7c@mail.gmail.com \
--to=marcone@xs4all.nl \
--cc=git@vger.kernel.org \
--cc=nanako3@lavabit.com \
--cc=raa.lkml@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 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).