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, neil@ossau.uklinux.net
Subject: Re: Archive of library modules for Guile
Date: Sun, 07 Mar 2004 19:17:06 +0100	[thread overview]
Message-ID: <E1B02pm-0001BH-00@surf.glug.org> (raw)
In-Reply-To: <87y8qg1ztz.fsf_-_@ivanova.rotty.yi.org> (message from Andreas Rottmann on Thu, 04 Mar 2004 14:55:36 +0100)

   From: Andreas Rottmann <a.rottmann@gmx.at>
   Date: Thu, 04 Mar 2004 14:55:36 +0100

   Detailed instructions on how this would happen will be provided with
   the archive announcement.  Thoughts?

my interest in (re-)organization of things at this level is at a trough
at the moment.  the MO is simple: capable programmers post code and
those things that strike my fancy i will use or adapt to my needs, if i
am able.  what code i write i post (capable or not ;-).

   And finally: what is the general feeling about such an archive among
   the Guile user (and developer) community?

probably any "general feeling" you can glean is illusory at best.  my
personal feeling is that separating users and programmers in the context
of guile is a mistake, and not realizing this as a mistake is another
mistake.  this is the same spew i've spewed before so i'll stop now.

thi


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


  parent reply	other threads:[~2004-03-07 18:17 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-01  3:32 Extended -e syntax Clinton Ebadi
2004-03-01  5:04 ` Andreas Rottmann
2004-03-01 11:10   ` Thien-Thi Nguyen
2004-03-01 14:27     ` Arch and Guile Andreas Rottmann
2004-03-01 19:04       ` ITLA (was Re: Arch and Guile) Tom Lord
2004-03-01 19:14         ` ITLA Andreas Rottmann
2004-03-01 21:55           ` ITLA Tom Lord
2004-03-02  0:11             ` ITLA Andreas Rottmann
2004-03-02  2:50               ` ITLA Tom Lord
2004-03-02 14:04                 ` ITLA Andreas Rottmann
2004-03-02  3:26             ` ITLA Miles Bader
2004-03-03 11:22           ` ITLA Neil Jerram
2004-03-03 11:55             ` ITLA Andreas Rottmann
2004-03-04 13:55             ` Archive of library modules for Guile Andreas Rottmann
2004-03-04 20:49               ` Neil Jerram
2004-03-04 23:00                 ` Andreas Rottmann
2004-03-07 17:33               ` Thamer Al-Harbash
2004-03-07 18:17               ` Thien-Thi Nguyen [this message]
2004-03-01 23:07       ` Arch and Guile Thien-Thi Nguyen
2004-03-02  0:23         ` Andreas Rottmann
2004-03-03 13:01           ` Thien-Thi Nguyen
2004-03-01 11:21 ` Extended -e syntax Thien-Thi Nguyen
2004-03-01 20:20 ` Christopher Cramer
2004-03-02  4:55   ` Clinton Ebadi
2004-03-06 15:47 ` ttn's build system [was: Extended -e syntax] Andreas Rottmann
2004-03-10 18:59   ` ttn's build system Andreas Rottmann
2004-03-10 22:28   ` ttn's build system [was: Extended -e syntax] Clinton Ebadi
2004-03-10 23:22   ` Tom Lord

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=E1B02pm-0001BH-00@surf.glug.org \
    --to=ttn@surf.glug.org \
    --cc=guile-user@gnu.org \
    --cc=neil@ossau.uklinux.net \
    --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).