git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: jidanni@jidanni.org
To: peff@peff.net
Cc: git@vger.kernel.org, 507476@bugs.debian.org
Subject: Re: user-manual.html invalid HTML
Date: Fri, 12 Dec 2008 10:47:27 +0800	[thread overview]
Message-ID: <87hc5ahzy8.fsf@jidanni.org> (raw)
In-Reply-To: 20081212023003.GD23128@sigill.intra.peff.net

>>>>> "JK" == Jeff King <peff@peff.net> writes:

JK> On Fri, Dec 12, 2008 at 04:32:15AM +0800, jidanni@jidanni.org wrote:
>> Please see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507476
>> Which it turns out didn't get forwarded to git@vger.kernel.org after all. 

JK> The versions I build locally have:

JK> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
JK>     "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">

JK> in each HTML file, which is added by asciidoc.  Maybe the package you
JK> are looking at was built with an older version of asciidoc that doesn't
JK> do this (I don't actually know the history of this feature, but it seems
JK> to me that this is something asciidoc should be doing, not git).

JK> -Peff

OK, adding 507476@bugs.debian.org to the CCs.

  reply	other threads:[~2008-12-12  2:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-03  1:32 X-Debbugs-Cc didn't make it to git@vger.kernel.org jidanni
2008-12-11 20:29 ` git-doc CSS dependent, breaks down in text browsers jidanni
2008-12-12  3:33   ` Jeff King
2008-12-11 20:32 ` user-manual.html invalid HTML jidanni
2008-12-12  2:30   ` Jeff King
2008-12-12  2:47     ` jidanni [this message]
2010-08-20  5:04       ` Jonathan Nieder
2010-08-21  6:21         ` Jeff King
2010-08-22  7:23           ` Junio C Hamano
2009-01-08 19:36 ` X-Debbugs-Cc didn't make it to git@vger.kernel.org jidanni

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87hc5ahzy8.fsf@jidanni.org \
    --to=jidanni@jidanni.org \
    --cc=507476@bugs.debian.org \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).