git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Pavan Kumar Sunkara <pavan.sss1991@gmail.com>
Cc: Drew Northup <drew.northup@maine.edu>, git@vger.kernel.org
Subject: Re: [PATCH] Documentation/Notes: Remove 'footnote:' warning
Date: Mon, 18 Jul 2011 00:51:08 -0500	[thread overview]
Message-ID: <20110718055108.GA4254@elie.gateway.2wire.net> (raw)
In-Reply-To: <CAK9CXBVSq_j7naHzVLMj=bW8WMKq_WfkDQP4zspkK_QizC26=g@mail.gmail.com>

Pavan Kumar Sunkara wrote:
> On Mon, Jul 18, 2011 at 3:28 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:

>> Good call.  This was fixed by Docbook XSL 1.76.0:
>>
>>        Norman Walsh: block.xsl; endnotes.xsl
>>
>>                Fix bug where simpara in footnote didn't work.
>>
>> The symptoms are a warning and a little extra vertical space after the
>> numberal "1." in the output.  I don't know if it is worth working
>> around or not.
>
> So, using newest version will not give us a warning?

Yes, when I run "make -C Documentation git-notes.1" I don't get the
warning or spurious blank line.  Sorry for the lack of clarity.
(That's no reason to not to adopt a workaround if it is pleasant, of
course.)

  reply	other threads:[~2011-07-18  5:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-16 22:30 [PATCH] Documentation/Notes: Remove 'footnote:' warning Pavan Kumar Sunkara
2011-07-17 13:11 ` Drew Northup
     [not found]   ` <CAK9CXBUAX42gCuRLWUpuvK6SSZXv1Cn4YNoFAfjRhouzd+thcw@mail.gmail.com>
2011-07-17 13:46     ` Pavan Kumar Sunkara
2011-07-17 21:58   ` Jonathan Nieder
2011-07-18  5:42     ` Pavan Kumar Sunkara
2011-07-18  5:51       ` Jonathan Nieder [this message]
2011-07-18  6:07         ` Pavan Kumar Sunkara
2011-07-18  7:13           ` Jonathan Nieder
2011-07-18  9:01             ` Pavan Kumar Sunkara
2011-07-19 20:43               ` Junio C Hamano

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=20110718055108.GA4254@elie.gateway.2wire.net \
    --to=jrnieder@gmail.com \
    --cc=drew.northup@maine.edu \
    --cc=git@vger.kernel.org \
    --cc=pavan.sss1991@gmail.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).