public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Joshua Saddler (nightmorph)" <nightmorph@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo commit in xml/htdocs/xsl: guide.xsl
Date: Fri, 26 Jun 2009 03:48:42 +0000	[thread overview]
Message-ID: <E1MK2Qc-0003Jl-EO@stork.gentoo.org> (raw)

nightmorph    09/06/26 03:48:42

  Modified:             guide.xsl
  Log:
  reverting robbat2's commit to 'fix' archives.gentoo.org, as it completely hosed every guidexml docuement we had. his change removed the Code Listing from every doc that had one. putting them back. we need to find some other solution for archives.gentoo.org that doesn't hurt all our other docs.

Revision  Changes    Path
1.243                xml/htdocs/xsl/guide.xsl

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/xsl/guide.xsl?rev=1.243&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/xsl/guide.xsl?rev=1.243&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/xsl/guide.xsl?r1=1.242&r2=1.243

Index: guide.xsl
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/xsl/guide.xsl,v
retrieving revision 1.242
retrieving revision 1.243
diff -u -r1.242 -r1.243
--- guide.xsl	17 Jun 2009 01:29:38 -0000	1.242
+++ guide.xsl	26 Jun 2009 03:48:42 -0000	1.243
@@ -1160,7 +1160,6 @@
 
     <a name="{$preid}"/>
     <table class="ntable" width="100%" cellspacing="0" cellpadding="0" border="0">
-      <xsl:if test="@plain!='true'">
         <tr>
           <td bgcolor="#7a5ada">
             <p class="codetitle">
@@ -1171,7 +1170,6 @@
             </p>
           </td>
         </tr>
-      </xsl:if>
       <tr>
         <td bgcolor="#eeeeff" align="left" dir="ltr">
           <pre>






             reply	other threads:[~2009-06-26  3:48 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-26  3:48 Joshua Saddler (nightmorph) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-03-14 19:24 [gentoo-commits] gentoo commit in xml/htdocs/xsl: guide.xsl Alex Legler (a3li)
2013-06-09 18:10 Robin H. Johnson (robbat2)
2013-06-09 17:35 Robin H. Johnson (robbat2)
2013-06-09 17:31 Robin H. Johnson (robbat2)
2013-06-09 17:30 Robin H. Johnson (robbat2)
2013-06-09 17:27 Robin H. Johnson (robbat2)
2013-06-09  1:15 Robin H. Johnson (robbat2)
2013-06-09  1:13 Robin H. Johnson (robbat2)
2012-06-18 10:30 Alec Warner (antarus)
2011-11-29 18:57 Sven Vermeulen (swift)
2011-04-01  4:49 Robin H. Johnson (robbat2)
2010-07-08 22:34 Robin H. Johnson (robbat2)
2010-06-18  5:21 Robin H. Johnson (robbat2)
2010-06-18  4:49 Robin H. Johnson (robbat2)
2009-07-01 16:33 Xavier Neys (neysx)
2009-06-26 16:31 Xavier Neys (neysx)
2009-06-17  1:29 Robin H. Johnson (robbat2)
2009-02-01 15:00 Xavier Neys (neysx)
2008-09-03 21:46 Joshua Saddler (nightmorph)
2008-05-09 19:57 Ned Ludd (solar)
2008-05-09 19:18 Ned Ludd (solar)
2008-03-28 23:35 Xavier Neys (neysx)
2008-03-09 13:01 Xavier Neys (neysx)
2008-01-22 20:36 Xavier Neys (neysx)
2008-01-19 14:18 Xavier Neys (neysx)
2007-11-15  8:16 Xavier Neys (neysx)
2007-11-06  0:09 Xavier Neys (neysx)
2007-10-04 19:38 Xavier Neys (neysx)
2007-09-07  9:15 Xavier Neys, French Docs Lead (neysx)

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=E1MK2Qc-0003Jl-EO@stork.gentoo.org \
    --to=nightmorph@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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