unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: NEWS entries -- user-visible?
Date: Fri, 19 Jun 2009 19:58:33 +0200	[thread overview]
Message-ID: <861vpghzqu.fsf@gnu.org> (raw)
In-Reply-To: 87fxdwcdyv.fsf@arudy.ossau.uklinux.net

Neil Jerram <neil@ossau.uklinux.net> writes:

> ludo@gnu.org (Ludovic Courtès) writes:
>
>> I think GNU users, especially on non-GNU platforms (proprietary Unices,
>> etc.), have come to know what Gnulib is, and to appreciate it
>> (hopefully), which is why I thought it would make sense to mention it.
>
> Perhaps it should go in a new section of the NEWS, with title
> something like `News about how Guile itself is developed'.  Then we
> might also mention using Git, libunistring etc.  But there's a risk
> we'd just end up duplicated information in README and HACKING, I
> think.

I was really thinking of GNU users, not GNU hackers.  I think users, not
just hackers, may be interested in knowing Gnulib is used.

That said, if you feel otherwise, it probably means that things aren't
that clearcut, so I won't insist on keeping this entry.

Thanks,
Ludo'.





  reply	other threads:[~2009-06-19 17:58 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 [this message]
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
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=861vpghzqu.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-devel@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).