unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
	"Thien-Thi Nguyen" <ttn@gnuvola.org>,
	guile-devel@gnu.org
Subject: Re: Do you recognize these modules?
Date: Wed, 11 Jul 2012 12:44:58 +0200	[thread overview]
Message-ID: <87sjcypoet.fsf@pobox.com> (raw)
In-Reply-To: <CA+U71=NbRGC2zOBN_Mxt0RxG7f30BGJYHmSWv_pqLiJs3J-cVQ@mail.gmail.com> (Noah Lavine's message of "Tue, 10 Jul 2012 23:02:29 -0400")

On Wed 11 Jul 2012 05:02, Noah Lavine <noah.b.lavine@gmail.com> writes:

> I'm sorry to miss 2.0.6 by only a few days, but I have turned this
> documentation into some patches. Here they are; I think they are ready
> to apply to stable-2.0.

Cool.  I applied the first one.  When applying the rest, I got:

    /home/wingo/src/guile/doc/ref//lineio.texi:12: Prev reference to nonexistent node `Double-Key Hash Tables' (perhaps incorrect sectioning?).
    /home/wingo/src/guile/doc/ref//hcons.texi:12: `Eq? Hash Consing' has no Up field (perhaps incorrect sectioning?).
    /home/wingo/src/guile/doc/ref//gap-buffer.texi:12: Next reference to nonexistent node `Double-Key Hash Tables' (perhaps incorrect sectioning?).
    /home/wingo/src/guile/doc/ref//guile.texi:375: Menu reference to nonexistent node `Double-Key Hash Tables' (perhaps incorrect sectioning?).
    /home/wingo/src/guile/doc/ref//hcons.texi:12: warning: unreferenced node `Eq? Hash Consing'.
    makeinfo: Removing output file `guile.info' due to errors; use --force to preserve.
    make[4]: *** [guile.info] Error 1

As Thien-Thi suggests, it's probably good to filter out the
@twerpcommentary etcetera in your next patches.

Cheers,

Andy
-- 
http://wingolog.org/



  parent reply	other threads:[~2012-07-11 10:44 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-01 22:26 Do you recognize these modules? Noah Lavine
2012-05-01 23:22 ` Thien-Thi Nguyen
2012-05-02 15:26   ` Noah Lavine
2012-05-14  8:04     ` Thien-Thi Nguyen
2012-05-14 10:52       ` Noah Lavine
2012-05-14 12:59         ` David Kastrup
2012-05-14 13:59           ` Noah Lavine
2012-05-14 14:12             ` David Kastrup
2012-05-14 12:44       ` Ludovic Courtès
2012-05-14 17:00         ` Thien-Thi Nguyen
2012-05-14 17:30           ` Noah Lavine
2012-05-15 20:14           ` Andy Wingo
2012-05-25  8:53             ` Thien-Thi Nguyen
2012-05-25 12:48               ` Andy Wingo
2012-05-25 17:02                 ` Thien-Thi Nguyen
2012-07-11  3:02                   ` Noah Lavine
2012-07-11  7:21                     ` Thien-Thi Nguyen
2012-07-11 10:44                     ` Andy Wingo [this message]
2012-07-11 15:20                       ` Noah Lavine
2012-07-11 17:59                         ` Noah Lavine
2012-08-25 22:27                           ` Noah Lavine
2012-08-26 20:47                             ` Ludovic Courtès
2013-03-23 10:36             ` Thien-Thi Nguyen

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: https://www.gnu.org/software/guile/

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

  git send-email \
    --in-reply-to=87sjcypoet.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=noah.b.lavine@gmail.com \
    --cc=ttn@gnuvola.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 read-only IMAP folder(s) and NNTP newsgroup(s).