From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: Node `...' previously defined at line 29776.
Date: Wed, 02 May 2007 23:18:20 +0200 [thread overview]
Message-ID: <v9y7k6udpf.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <b4mejm010dq.fsf@jpl.org>
On Wed, May 02 2007, Katsumi Yamaoka wrote:
>>>>>> In <m3wszs9h0k.fsf@pigpen.waxrat.com> Michael Cook wrote:
>> /local/gnus/repo/gnus/texi//doclicense.texi:2: Node `GNU Free Documentation License' previously defined at line 29776.
>
> This happens also when MAKEINFO=no.
This was due to the latest sync from Emacs. I fixed it by updating
doclicense.texi to the version in Emacs (version 1.2 of the GFDL)
including the arch tag. I think that we should always keep those in
sync. Miles, I hope using the same arch tag is The Right Way to
achieve this.
> In addition, gnus.texi says: This manual corresponds to No Gnus
> v0.5.
I've updated all version numbers to No Gnus 0.7.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2007-05-02 21:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 1:00 Michael Cook
2007-05-02 1:26 ` Katsumi Yamaoka
2007-05-02 21:18 ` Reiner Steib [this message]
2007-05-03 2:47 ` Miles Bader
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=v9y7k6udpf.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=ding@gnus.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).