git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Beller <sbeller@google.com>
To: Guillaume Castagnino <casta+github@xwing.info>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH] use filetest pragma to work with ACL
Date: Wed, 18 Oct 2017 13:05:08 -0700	[thread overview]
Message-ID: <CAGZ79kZG=nk+U815mWhSMDHqa=UHSwCc_PbQcaTRBA8DBKoWrw@mail.gmail.com> (raw)
In-Reply-To: <0102015f310e24b9-b96378f3-a029-4110-80dd-e454522e2cb7-000000@eu-west-1.amazonses.com>

On Wed, Oct 18, 2017 at 12:55 PM, Guillaume Castagnino
<casta+github@xwing.info> wrote:
> From: Guillaume Castagnino <casta@xwing.info>
>
> as stated in comment in https://github.com/git/git/commit/46a13857fc036b54ac2ddd0a218e5cc171aa7bd9#diff-00703a794a540acf45e225abd6aeda3b the referenced commit is broken when using ACL and not basic UNIX rights.
> this commit handle ACL too

Thanks for contributing to Git!

Please see Documentation/SubmittingPatches for details,
tl;dr:
* If you can legally agree with
   https://developercertificate.org/
   add a line "Signed-off-by: NAME <email>"
* Please give a more descriptive commit message.
  Usually we phrase the commit subject as
  "area: do thing", you have the "do thing" part,
  but the area is unclear. Maybe:
      gitweb: use filetest to allow ACLs

* Keep the message text roughly at 70 characters per line,
  as that is easier to read in e.g. git-show.

* Instead of linking to github, we usually only refer to the commit, e.g.

   In commit 46a1385 (gitweb: skip unreadable subdirectories, 2017-07-18)
   we forgot to handle non-unix ACLs as well. Fix this.

* Do we need a test/documentation for this?

Thanks,
Stefan

> ---
>  gitweb/gitweb.perl | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
> index 9208f42ed1753..0ee7f304ce2b1 100755
> --- a/gitweb/gitweb.perl
> +++ b/gitweb/gitweb.perl
> @@ -3072,6 +3072,7 @@ sub git_get_projects_list {
>                                 # only directories can be git repositories
>                                 return unless (-d $_);
>                                 # need search permission
> +                               use filetest 'access';
>                                 return unless (-x $_);
>                                 # don't traverse too deep (Find is super slow on os x)
>                                 # $project_maxdepth excludes depth of $projectroot
>
> --
> https://github.com/git/git/pull/416

  reply	other threads:[~2017-10-18 20:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-18 19:55 [PATCH] use filetest pragma to work with ACL Guillaume Castagnino
2017-10-18 20:05 ` Stefan Beller [this message]
2017-10-18 21:24 ` Jeff King
2017-10-19  7:53   ` Guillaume Castagnino
2017-10-19 16:13     ` Jeff King
2017-10-24  5:02       ` Junio C Hamano

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='CAGZ79kZG=nk+U815mWhSMDHqa=UHSwCc_PbQcaTRBA8DBKoWrw@mail.gmail.com' \
    --to=sbeller@google.com \
    --cc=casta+github@xwing.info \
    --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 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).