From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: <gdb-patches@sourceware.org>
Subject: [RFA] contrib/ari: Avoid permission issue for script
Date: Thu, 01 Nov 2012 21:56:00 -0000 [thread overview]
Message-ID: <000f01cdb87b$c193f5c0$44bbe140$@muller@ics-cnrs.unistra.fr> (raw)
Generating a web page from the newly committed
Files in src/gdb/contrib/ari
directory is almost possible without change.
But I still have the problem of the permissions
of the script files...
And I still don't know if (and if yes, how)
I can set file permissions in the CVS repository...
I can lift the problem for the main script,
by calling it using:
sh ../../src/gdb/contrib/ari/ create-web-ari-in-src.sh,
but this script calls update-web-ari.sh script
without using '. script'...
Is this OK?
Other question:
Should I add myself as contrib/ari maintainer?
2012-11-01 Pierre Muller <muller@ics.u-strasbg.fr>
* contrib/ari/create-web-ari-in-src.sh: Avoid problem if script
is not executable.
Index: create-web-ari-in-src.sh
===================================================================
RCS file: /cvs/src/src/gdb/contrib/ari/create-web-ari-in-src.sh,v
retrieving revision 1.1
diff -u -r1.1 create-web-ari-in-src.sh
--- create-web-ari-in-src.sh 1 Nov 2012 21:22:27 -0000 1.1
+++ create-web-ari-in-src.sh 1 Nov 2012 21:48:21 -0000
@@ -67,7 +67,7 @@
fi
# Launch update-web-ari.sh in same directory as current script.
-${scriptpath}/update-web-ari.sh ${srcdir} ${tempdir} ${webdir} gdb
+. ${scriptpath}/update-web-ari.sh ${srcdir} ${tempdir} ${webdir} gdb
if [ -f "${webdir}/index.html" ] ; then
echo "ARI output can be viewed in file \"${webdir}/index.html\""
next reply other threads:[~2012-11-01 21:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-01 21:56 Pierre Muller [this message]
[not found] <11045.9555559375$1351807023@news.gmane.org>
2012-11-02 17:27 ` Tom Tromey
2012-11-02 17:31 ` Pedro Alves
2012-11-02 18:25 ` Pierre Muller
2012-11-02 18:33 ` Pedro Alves
2012-11-02 18:44 ` Andreas Schwab
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='000f01cdb87b$c193f5c0$44bbe140$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=gdb-patches@sourceware.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