From: Tim Bird <tim.bird@am.sony.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: "Jörn Engel" <joern@logfs.org>,
linux-embedded <linux-embedded@vger.kernel.org>,
"linux kernel" <linux-kernel@vger.kernel.org>
Subject: execute bit on scripts (was Re: [PATCH] add diffconfig utility)
Date: Tue, 10 Jun 2008 14:33:23 -0700 [thread overview]
Message-ID: <484EF323.7000809@am.sony.com> (raw)
In-Reply-To: <20080610211841.GA23855@uranus.ravnborg.org>
Sam Ravnborg wrote:
> I will merge it if the feedabck is positive and eventual feedback
> is dealt with. (And Tim reminds me to do so in a week or so).
Thanks.
> I take most of the random scripts in scripts/ via kbuild.git.
OK - sounds like you're the right person to ask a question
that has been nagging me.
Is there a proper way to get the execute bit set in the git tree
on patches that contain scripts? I think patches
produced by git have something that sets the file permissions?
Is this something that can (or should) be hand-added to
a non-git patch? (I use quilt).
I put that blurb in the patch description about doing a
'chmod a+x', but that doesn't seem reliable.
-- Tim
=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Corporation of America
=============================
next prev parent reply other threads:[~2008-06-10 21:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 19:41 [PATCH] add diffconfig utility Tim Bird
2008-06-10 21:02 ` Jörn Engel
2008-06-10 21:18 ` Sam Ravnborg
2008-06-10 21:33 ` Tim Bird [this message]
2008-06-10 22:26 ` execute bit on scripts (was Re: [PATCH] add diffconfig utility) Jan Engelhardt
2008-06-10 21:21 ` [PATCH] add diffconfig utility Sam Ravnborg
2008-06-11 0:25 ` Tim Bird
2008-06-11 11:28 ` Geert Uytterhoeven
2008-06-11 18:23 ` Tim Bird
2008-06-12 13:19 ` Sam Ravnborg
2008-06-12 16:07 ` Tim Bird
2008-06-24 17:56 ` [PATCH] add diffconfig utility (v2) Tim Bird
2008-06-27 21:10 ` Sam Ravnborg
2008-06-10 22:07 ` [PATCH] add diffconfig utility David Woodhouse
2008-06-10 22:33 ` Tim Bird
2008-06-10 23:02 ` Arjan van de Ven
2008-06-10 23:10 ` David Woodhouse
2008-06-11 6:59 ` Holger Schurig
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=484EF323.7000809@am.sony.com \
--to=tim.bird@am.sony.com \
--cc=joern@logfs.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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).