git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Parametrize asciidoc and add --unsafe
Date: Wed, 25 Jan 2006 01:52:22 -0500	[thread overview]
Message-ID: <1138171942.27366.104.camel@dv> (raw)
In-Reply-To: <7vzmll2h5h.fsf@assigned-by-dhcp.cox.net>

On Tue, 2006-01-24 at 18:08 -0800, Junio C Hamano wrote:
> Pavel Roskin <proski@gnu.org> writes:
> 
> > Including files from the parent directory is considered unsafe by
> > asciidoc 7.1.0.  This is used in git.txt, which includes ../README.
> 
> Is copying/linking README down when we build documentation a
> more conservative option, I wonder?

I considered this possibility.  I don't have a strong preference.  The
argument in favor of "--unsafe" is that adding a make target is more
intrusive that adding a switch.  Besides, we may want to include more
files from other directories.

> Does asciidoc prior to 7.1.0 do sensible thing given an --unsafe
> option?  If not, how does one override ASCIIDOC from the command
> line to the toplevel "make"?

Good question.  I misunderstood the asciidoc changelog.  Older versions
(before 7.0.4) understand "--safe", but not "--unsafe".  Since version
7.0.4 is less than 2 months old, it would be reasonable not to go ahead
with my patch right now.

Let's make a copy for now.  Symbolic linking doesn't work - asciidoc
recognizes and rejects symlinks.

---
[PATCH] Don't include ../README in git.txt - make a local copy

asciidoc 7.0.4 and newer considers such includes from parent directory
unsafe.

Signed-off-by: Pavel Roskin <proski@gnu.org>
---

 Documentation/.gitignore |    1 +
 Documentation/Makefile   |    9 ++++++---
 Documentation/git.txt    |    2 +-
 3 files changed, 8 insertions(+), 4 deletions(-)

diff --git a/Documentation/.gitignore b/Documentation/.gitignore
index 9fef490..c87c61a 100644
--- a/Documentation/.gitignore
+++ b/Documentation/.gitignore
@@ -4,3 +4,4 @@
 *.7
 howto-index.txt
 doc.dep
+README
diff --git a/Documentation/Makefile b/Documentation/Makefile
index a65fb1b..a3bca86 100644
--- a/Documentation/Makefile
+++ b/Documentation/Makefile
@@ -62,11 +62,14 @@ doc.dep : $(wildcard *.txt) build-docdep
 
 -include doc.dep
 
-git.7: ../README
+git.7: README
+
+README: ../README
+	cp $< $@
 
 
 clean:
-	rm -f *.xml *.html *.1 *.7 howto-index.txt howto/*.html doc.dep
+	rm -f *.xml *.html *.1 *.7 howto-index.txt howto/*.html doc.dep README
 
 %.html : %.txt
 	asciidoc -b xhtml11 -d manpage -f asciidoc.conf $<
@@ -77,7 +80,7 @@ clean:
 %.xml : %.txt
 	asciidoc -b docbook -d manpage -f asciidoc.conf $<
 
-git.html: git.txt ../README
+git.html: git.txt README
 
 glossary.html : glossary.txt sort_glossary.pl
 	cat $< | \
diff --git a/Documentation/git.txt b/Documentation/git.txt
index 25bcb84..e8ef3ef 100644
--- a/Documentation/git.txt
+++ b/Documentation/git.txt
@@ -586,7 +586,7 @@ git Diffs
 
 Discussion[[Discussion]]
 ------------------------
-include::../README[]
+include::README[]
 
 Authors
 -------


-- 
Regards,
Pavel Roskin

      reply	other threads:[~2006-01-25  6:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-24 22:15 [PATCH] Parametrize asciidoc and add --unsafe Pavel Roskin
2006-01-25  2:08 ` Junio C Hamano
2006-01-25  6:52   ` Pavel Roskin [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=1138171942.27366.104.camel@dv \
    --to=proski@gnu.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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).