From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Brandon Casey <casey@nrlssc.navy.mil>
Cc: git@vger.kernel.org, Brandon Casey <drafnel@gmail.com>
Subject: Re: [PATCH 3/5] t/t1304: use 'test -r' to test readability rather than looking at mode bits
Date: Mon, 15 Mar 2010 18:33:53 +0100 [thread overview]
Message-ID: <vpq3a017am6.fsf@bauges.imag.fr> (raw)
In-Reply-To: <YowxgPZqaOkg2MZzY1CxL61O63C5ULimj64t69Bc-wsW3IlWf4Zc9WmA3ihonAb8UtR5thcko00@cipher.nrlssc.navy.mil> (Brandon Casey's message of "Mon\, 15 Mar 2010 12\:14\:35 -0500")
Brandon Casey <casey@nrlssc.navy.mil> writes:
> - -r--r-----*)
> - : happy
> - ;;
> + test -r "$1" &&
Maybe it makes sense to ask for -r--?-----* instead, to make sure we
don't give the read bit to anyone. But that's not really important
since we're protected by the directory's permission anyway.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2010-03-15 17:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 17:14 [PATCH 0/5] tweak t1304 ACL tests so they work on Solaris Brandon Casey
2010-03-15 17:14 ` [PATCH 1/5] t/t1304: avoid -d option to setfacl Brandon Casey
2010-03-15 17:14 ` [PATCH 2/5] t/t1304: set the Default ACL base entries Brandon Casey
2010-03-15 17:14 ` [PATCH 3/5] t/t1304: use 'test -r' to test readability rather than looking at mode bits Brandon Casey
2010-03-15 17:33 ` Matthieu Moy [this message]
2010-03-15 17:51 ` Brandon Casey
2010-03-15 17:14 ` [PATCH 4/5] t/t1304: set the mask ACL that is checked in check_perms_and_acl Brandon Casey
2010-03-15 17:37 ` Matthieu Moy
2010-03-15 18:17 ` Brandon Casey
2010-03-15 18:35 ` [PATCH 4/5 v2] t/t1304: set the ACL effective rights mask Brandon Casey
2010-03-15 18:53 ` Matthieu Moy
2010-03-15 17:14 ` [PATCH 5/5] t/t1304: make a second colon optional in the mask ACL check Brandon Casey
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=vpq3a017am6.fsf@bauges.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=casey@nrlssc.navy.mil \
--cc=drafnel@gmail.com \
--cc=git@vger.kernel.org \
/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.