From: Alex Riesen <raa.lkml@gmail.com>
To: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
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: Mon, 7 Jul 2008 01:11:46 +0200 [thread overview]
Message-ID: <20080706231146.GE17659@steel.home> (raw)
In-Reply-To: <486FD4FB.6070803@ramsay1.demon.co.uk>
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).
next prev parent reply other threads:[~2008-07-06 23:12 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 [this message]
2008-07-08 22:27 ` Ramsay Jones
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=20080706231146.GE17659@steel.home \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ramsay@ramsay1.demon.co.uk \
/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).