From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: Getting no messages
Date: Sat, 26 Oct 2002 16:28:09 -0500 [thread overview]
Message-ID: <87u1j86gba.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <m3wuo5gt1x.fsf@laruns.ossau.uklinux.net> (Neil Jerram's message of "26 Oct 2002 15:42:50 +0100")
Neil Jerram <neil@ossau.uklinux.net> writes:
> Personally I find parallel-branch development (which I do for
> applicable doc fixes and enhancements) to be an additional burden that
> I would prefer not to have. I think it's easier all round if we
> restrict 1.6.x to bug fixes (broadly speaking), only put new stuff
> into 1.7.x, and look forward to 1.8 sooner rather than later.
I totally agree about getting 1.8 out ASAP, but I consider these fixes
bug-fixes:
- srfi headers were ommitted in 1.6.0.
- emacs stuff was broken.
- ltdl was broken.
I'd be perfectly happy if the only 1.6.X releases after 1.6.1 are doc
updates, and debian/* commits. I may even leave the debian/* out and
save that for 1.8...
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-10-26 21:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 17:30 Getting no messages Dirk Herrmann
2002-10-25 21:44 ` Rob Browning
2002-10-26 8:27 ` Dirk Herrmann
2002-10-26 12:13 ` Neil Jerram
2002-10-26 14:42 ` Neil Jerram
2002-10-26 19:35 ` Marius Vollmer
2002-10-26 21:29 ` Neil Jerram
2002-10-26 21:28 ` Rob Browning [this message]
2002-10-26 16:50 ` Rob Browning
2002-10-26 14:43 ` rm
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=87u1j86gba.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.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).