mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Martin Waitz <tali@admingilde.org>
To: Andrew Morton <akpm@osdl.org>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: [PATCH] docbook: fix escaping of kernel-doc
Date: Fri, 18 Mar 2005 12:16:58 +0100	[thread overview]
Message-ID: <20050318111658.GM8617@admingilde.org> (raw)
In-Reply-To: <20050314004712.4746f2cf.akpm@osdl.org>

[-- Attachment #1: Type: text/plain, Size: 998 bytes --]

hoi :)

the following patch fixes a bug I introduced with the last patches
of the DocBook generation.

Signed-off-by: Martin Waitz <tali@admingilde.org>

---
Please apply.

... and I really have to redo my bitkeeper repository as it
is full of merge artifacts as BK did not note the fact that
the patches were applied using normal patches.

I guess I have to use one complete tree per patch and recreate
the public repo as a combination of the individual ones.
Alternatives?

diff -Nru a/scripts/kernel-doc b/scripts/kernel-doc
--- a/scripts/kernel-doc	2005-03-18 11:51:17 +01:00
+++ b/scripts/kernel-doc	2005-03-18 11:51:17 +01:00
@@ -1626,11 +1655,11 @@
 
 # replace <, >, and &
 sub xml_escape($) {
-	shift;
-	s/\&/\\\\\\amp;/g;
-	s/\</\\\\\\lt;/g;
-	s/\>/\\\\\\gt;/g;
-	return $_;
+	my $text = shift;
+	$text =~ s/\&/\\\\\\amp;/g;
+	$text =~ s/\</\\\\\\lt;/g;
+	$text =~ s/\>/\\\\\\gt;/g;
+	return $text;
 }
 
 sub process_file($) {


-- 
Martin Waitz

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

       reply	other threads:[~2005-03-18 11:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200503112034.j2BKYMli008385@shell0.pdx.osdl.net>
     [not found] ` <20050314081319.GD8617@admingilde.org>
     [not found]   ` <20050314004712.4746f2cf.akpm@osdl.org>
2005-03-18 11:16     ` Martin Waitz [this message]
2005-03-18 11:22       ` Andrew Morton

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=20050318111658.GM8617@admingilde.org \
    --to=tali@admingilde.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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

all inboxes | Powered by JetHome®