Gnus development mailing list
 help / color / mirror / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Reiner Steib'" <Reiner.Steib@gmx.de>, "'Juri Linkov'" <juri@jurta.org>
Cc: ding@gnus.org, emacs-devel@gnu.org
Subject: RE: 23.0.60; GNUS manual, `T' - bad nodes
Date: Mon, 16 Jun 2008 10:31:03 -0700	[thread overview]
Message-ID: <000801c8cfd6$c0b2e680$c2b22382@us.oracle.com> (raw)
In-Reply-To: <v9abhm5okb.fsf@marauder.physik.uni-ulm.de>

FWIW, I expected to receive this from bug-gnu-emacs, or perhaps
emacs-pretest-bug (where I submitted the bug), not from emacs-devel.

I admit it. I'm lost in the bug mails labyrinth.
I have no idea what to expect anymore.

> From: Reiner Steib Sent: Sunday, June 15, 2008 3:19 PM
> To: Juri Linkov Cc: Drew Adams; emacs-devel@gnu.org; ding@gnus.org
> Subject: Re: 23.0.60; GNUS manual, `T' - bad nodes
> On Thu, Jun 12 2008, Reiner Steib wrote:
> > On Thu, Jun 12 2008, Juri Linkov wrote:
> >> This doesn't work because Gnus uses invalid characters in node
> >> names.  See (info "(texinfo) Node Line Requirements") that says:
> [...]
> > I don't have time to deal with this now[1].  Could some assign this
> > (part of the) bug to Gnus in the bug tracker, please?  (It also
> > applies to Emacs 22.2 / Gnus 5.10.x.)
> 
> Fixed in v5-10.  It will propagate to Emacs_22 and to the trunk (Emacs
> and Gnus) eventually.





      reply	other threads:[~2008-06-16 17:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <00c101c8cb88$ddf48700$0200a8c0@us.oracle.com>
     [not found] ` <873anjocc8.fsf@jurta.org>
2008-06-12  6:23   ` Reiner Steib
2008-06-15 22:19     ` Reiner Steib
2008-06-16 17:31       ` Drew Adams [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='000801c8cfd6$c0b2e680$c2b22382@us.oracle.com' \
    --to=drew.adams@oracle.com \
    --cc=Reiner.Steib@gmx.de \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=juri@jurta.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;
as well as URLs for NNTP newsgroup(s).