linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Georg Nikodym" <georgn@somanetworks.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: georgn@somanetworks.com, linux-kernel@vger.kernel.org, lm@bitmover.com
Subject: [PATCH] Makefile
Date: Mon, 4 Dec 2000 16:24:46 -0500 (EST)	[thread overview]
Message-ID: <14892.2974.153654.949301@somanetworks.com> (raw)


When making the docs, the top-level Makefile unconditionally chmod's
three scripts.

Under BitKeeper, things are normally left read-only and the above mode
change is flagged as an error in subsequent BK operations.

BK is can and does track file modes, so BK users can:

	bk chmod +x scripts/docgen scripts/gen-all-syms scripts/kernel-doc
	(bk commit)

The following patch will not harm BK users and behave as always for
others.


===== Makefile 1.37 vs edited =====
--- 1.37/Makefile	Fri Nov 17 04:47:41 2000
+++ edited/Makefile	Mon Dec  4 16:15:16 2000
@@ -423,9 +423,15 @@
 	sync
 
 sgmldocs: 
-	chmod 755 $(TOPDIR)/scripts/docgen
-	chmod 755 $(TOPDIR)/scripts/gen-all-syms
-	chmod 755 $(TOPDIR)/scripts/kernel-doc
+	if [ ! -x $(TOPDIR)/scripts/docgen ]; then \
+		chmod 755 $(TOPDIR)/scripts/docgen ; \
+	fi ;
+	if [ ! -x $(TOPDIR)/scripts/gen-all-syms ]; then \
+		chmod 755 $(TOPDIR)/scripts/gen-all-syms ; \
+	fi
+	if [ ! -x $(TOPDIR)/scripts/kernel-doc ]; then \
+		chmod 755 $(TOPDIR)/scripts/kernel-doc ; \
+	fi
 	$(MAKE) -C $(TOPDIR)/Documentation/DocBook books
 
 psdocs: sgmldocs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

                 reply	other threads:[~2000-12-04 21:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=14892.2974.153654.949301@somanetworks.com \
    --to=georgn@somanetworks.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    --cc=torvalds@transmeta.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 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).