From: Ramsay Jones <ramsay@ramsay1•demon.co.uk>
To: Alex Riesen <raa.lkml@gmail•com>
Cc: GIT Mailing-list <git@vger•kernel.org>,
Junio C Hamano <gitster@pobox•com>
Subject: Re: "make test" works again (sort-of) on cygwin.
Date: Tue, 08 Jul 2008 23:27:08 +0100 [thread overview]
Message-ID: <4873E9BC.5040708@ramsay1.demon.co.uk> (raw)
In-Reply-To: <20080706231146.GE17659@steel.home>
Alex Riesen wrote:
> Ramsay Jones, Sat, Jul 05, 2008 22:09:31 +0200:
>> Alex Riesen wrote:
>>> Ramsay Jones, Thu, Jul 03, 2008 19:44:28 +0200:
>>>
>>>> Anyhow, the "sort-of" in the subject line, relates to the fact that
>>>> I am seeing some test failures. In particular, all tests in
>>>> t0004-unwritable.sh and tests 21->24 in t3700-add.sh. All of these
>>>> tests involve chmod/permissions ...
>>> Don't run "make test" as root (or "backup operator" on windows).
>>> OTOH, a windows machine is almost useless, unless you're a member of
>>> local administrators group (which includes "backup" permission).
>>>
>> Ah, yes... I am a "Computer administator" aren't I ;-) I totally forgot!
>>
>> Hmm, but is that really the reason for these failures? After all, (referring
>> to the example you snipped) the permissions are respected for creating
>> files in the directory, just not directories. Is the "root" user on
>> windows only selectively omnipotent?
>
> It is (it is the backup operators who can read open, even locked,
> files), but it is boringly hard to find when and where. You can try
> reading MSDN (or better don't, you'll live longer if you don't).
>
>
Yeah, I'm afraid I've had to serve that sentence (several times) in
the past; I'm still trying to figure out what my crime was... ;P
ATB,
Ramsay Jones
next prev parent reply other threads:[~2008-07-09 17:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 17:44 "make test" works again (sort-of) on cygwin Ramsay Jones
2008-07-03 20:26 ` Alex Riesen
2008-07-05 20:09 ` Ramsay Jones
2008-07-06 23:11 ` Alex Riesen
2008-07-08 22:27 ` Ramsay Jones [this message]
2008-07-04 0:04 ` Johannes Schindelin
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=4873E9BC.5040708@ramsay1.demon.co.uk \
--to=ramsay@ramsay1$(echo .)demon.co.uk \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=raa.lkml@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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