unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@surf.glug.org>
Cc: guile-user@gnu.org
Subject: Re: mkpimmc and friends
Date: Mon, 22 Mar 2004 22:32:24 +0100	[thread overview]
Message-ID: <E1B5X20-0000kZ-00@surf.glug.org> (raw)
In-Reply-To: <87brmozr0f.fsf@buug.org> (message from Ian Zimmerman on 22 Mar 2004 10:16:32 -0800)

   From: Ian Zimmerman <itz@buug.org>
   Date: 22 Mar 2004 10:16:32 -0800

   I am confused about guile versions.  I have installed 1.6 thinking it
   was the latest stable one.  If features are still being added to 1.4,
   what is 1.5 and 1.6 for?

i "cvs update" from 1.6 (and from HEAD, fwiw) every once in a while to
see if interesting bugfixes, documentation and new features show up (the
cvs commits mailing list seems to have been suspended indefinitely since
savannah was cracked a few months ago), and update 1.4.x w/ the tasty
bits that i find, when i find time to do so.

other people accept those versions as-is for their own reasons.  i don't
speak for them, although strangely enough, sometimes they like to speak
for me.  it can be very confusing at first glance, i agree.  best thing
to do is figure out what features you like and then find and/or build
the system that supports those features.  version numbers are labels,
useful at times but subject to misapplication and misinterpretation.
likewise the word "stable".  perhaps you know all this already.

thi


_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user


  parent reply	other threads:[~2004-03-22 21:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-22 12:30 mkpimmc and friends Thien-Thi Nguyen
2004-03-22 18:16 ` Ian Zimmerman
2004-03-22 19:09   ` Paul Jarc
2004-03-22 21:32   ` Thien-Thi Nguyen [this message]
2004-03-22 23:56   ` Christopher Cramer

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=E1B5X20-0000kZ-00@surf.glug.org \
    --to=ttn@surf.glug.org \
    --cc=guile-user@gnu.org \
    --cc=ttn@glug.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).