unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: NEWS entries -- user-visible?
Date: Mon, 29 Jun 2009 20:19:34 +0100	[thread overview]
Message-ID: <874otyx2yh.fsf@arudy.ossau.uklinux.net> (raw)
In-Reply-To: <87ljnds1zo.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sun\, 28 Jun 2009 01\:14\:51 +0200")

ludo@gnu.org (Ludovic Courtès) writes:

> Hi!
>
> Neil Jerram <neil@ossau.uklinux.net> writes:
>
>> "In addition to its manual, the package should have a file named
>> @file{NEWS} which contains a list of user-visible changes worth
>> mentioning.  ..."
>>
>> So I'd say that use of Gnulib (in general) should not be a NEWS item.
>> I think HACKING would be the right place to mention it - and it would
>> be just as accessible there (as in NEWS) to blurred users/developers.
>
> Sure, that's a possibility.
>
> (I think we don't disagree on what `NEWS' should contain, but on whether
> Gnulib qualifies as "user-visible".)

I would certainly agree that individual portability fixes should be in
NEWS.  Is that what you have in mind?

    Neil




  reply	other threads:[~2009-06-29 19:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-14 18:32 NEWS entries -- user-visible? Andy Wingo
2009-06-14 19:43 ` Julian Graham
2009-06-14 22:41   ` Neil Jerram
2009-06-18 20:48     ` Ludovic Courtès
2009-06-19 17:47       ` Neil Jerram
2009-06-19 17:58         ` Ludovic Courtès
2009-06-19 18:08           ` Neil Jerram
2009-06-19 18:13             ` Ludovic Courtès
2009-06-27 22:05               ` Neil Jerram
2009-06-27 23:14                 ` Ludovic Courtès
2009-06-29 19:19                   ` Neil Jerram [this message]
2009-06-29 21:01                     ` Ludovic Courtès
2009-06-14 20:39 ` Neil Jerram
2009-06-18 20:49 ` Ludovic Courtès

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=874otyx2yh.fsf@arudy.ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=guile-devel@gnu.org \
    --cc=ludo@gnu.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).