From: Hans Aberg <haberg-1@telia.com>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: reminder: read NEWS
Date: Sun, 30 Jan 2011 19:05:06 +0100 [thread overview]
Message-ID: <4DCE9AE5-8FCA-4937-886B-A0DCB76BC9F1@telia.com> (raw)
In-Reply-To: <m3tygq1t3i.fsf@unquote.localdomain>
On 30 Jan 2011, at 13:20, Andy Wingo wrote:
> I have noticed a number of questions coming across the list that
> almost
> seem to indicate that folks have not read the NEWS. I know this
> cannot
> be the case! ;)
>
> However if you're just jumping on the 2.0 train, take an hour or so
> out
> of your hacking to review the NEWS file. It is long, but should be
> exhaustive. If it's not, let us know. We'll be preparing a more
> condensed version for the release notes, but the long format is the
> most
> informative.
Since there are some significant changes between 1.8 and 2.0, perhaps
the manual might have a special section listing them. Searching the
1.9 GIT manual for "1.8" indicates that this information is currently
mainly given in a few footnotes.
In the case Guile is used as a library (as in LilyPond), their users
might consult the manual at need, but I suspect not the NEWS file.
prev parent reply other threads:[~2011-01-30 18:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-30 12:20 reminder: read NEWS Andy Wingo
2011-01-30 18:05 ` Hans Aberg [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
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=4DCE9AE5-8FCA-4937-886B-A0DCB76BC9F1@telia.com \
--to=haberg-1@telia.com \
--cc=guile-user@gnu.org \
--cc=wingo@pobox.com \
/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).