All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Jackson <Ian.Jackson@eu.citrix.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH 0 of 7] tools/check fixes for xen-unstable
Date: Fri, 7 Oct 2011 14:48:20 +0100	[thread overview]
Message-ID: <20111.804.769740.932387@mariner.uk.xensource.com> (raw)
In-Reply-To: <patchbomb.1317738109@probook.site>

Olaf Hering writes ("[Xen-devel] [PATCH 0 of 7] tools/check fixes for xen-unstable"):
> 
> Remove the need for executable permissions of some files in the SCM.

Thanks for this contribution but I'm afraid I don't really agree with
the need for this change.  It is simpler in our build system (which is
quite complicated enough already) just to execute these kind of
scripts directly.

If the arrangements you use for producing a source tree don't always
put the +x permissions back correctly, then I think that's something
that shouldn't be too hard to fix.  There should be no problem with
setting +x on files that don't need it (and if there is, we can
probably fix that) so you don't have to be 100% discriminating in that
fixup.

Ian.

      parent reply	other threads:[~2011-10-07 13:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-04 14:21 [PATCH 0 of 7] tools/check fixes for xen-unstable Olaf Hering
2011-10-04 14:21 ` [PATCH 1 of 7] tools/check: remove check_logging Olaf Hering
2011-10-04 14:21 ` [PATCH 2 of 7] tools/check: call all check_* scripts with shell Olaf Hering
2011-10-04 14:21 ` [PATCH 3 of 7] tools/check: update python version check Olaf Hering
2011-10-07 13:34   ` [PATCH 1 of 7] tools/check: remove check_logging [and 1 more messages] Ian Jackson
2011-10-04 14:21 ` [PATCH 4 of 7] tools: call xen-setup with shell Olaf Hering
2011-10-04 14:21 ` [PATCH 5 of 7] tools: call cross-install " Olaf Hering
2011-10-04 14:21 ` [PATCH 6 of 7] tools: call install-wrap " Olaf Hering
2011-10-04 14:21 ` [PATCH 7 of 7] tools: call etherboot/mkhex " Olaf Hering
2011-10-07 13:48 ` Ian Jackson [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=20111.804.769740.932387@mariner.uk.xensource.com \
    --to=ian.jackson@eu.citrix.com \
    --cc=olaf@aepfle.de \
    --cc=xen-devel@lists.xensource.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 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.