unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: guile-user@gnu.org
Subject: Re: updated $workbook/modules/modules-and-shared-libs.text
Date: Wed, 22 May 2002 00:40:44 -0700	[thread overview]
Message-ID: <E17AQjk-0002P8-00@giblet> (raw)
In-Reply-To: <874rh04xqy.fsf@raven.i.defaultvalue.org> (message from Rob Browning on Tue, 21 May 2002 23:23:01 -0500)

   From: Rob Browning <rlb@defaultvalue.org>
   Date: Tue, 21 May 2002 23:23:01 -0500

   Not exactly hearsays -- problems I've run in to directly while
   working on prgrams using guile, guile modules, and shared libraries
   extensively.

i'm not doubting your experience, just your way of sharing it.

it's better if you can share experiences directly (as bug reports or
other notes under $workbook) than as anecdotal asides.  a bug report
would be best, because it encourages us to think about and develop
testing framework to test for that bug, in addition to providing useful
documentation on your experience.

if you don't want to be formal, create $workbook/journal/rlb and add
notes there.  other people can organize the raw data to their needs; all
you have to do is make it available (in a precise way) in a place that's
easier to get to than requiring a possibly fruitless archive search.

asking people to search for specific information wastes their time and
shows you didn't value the information enough to use your write privs to
their best effect.  in the end, how can people trust your judgements if
they can't see your methods?

thi

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


  reply	other threads:[~2002-05-22  7:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-21 21:16 updated $workbook/modules/modules-and-shared-libs.text Thien-Thi Nguyen
     [not found] ` <20020521173935.5f721206.dsmith@altustech.com>
2002-05-21 22:16   ` Thien-Thi Nguyen
2002-05-21 22:30 ` Bill Gribble
2002-05-21 23:31   ` Thien-Thi Nguyen
2002-05-22  1:52 ` Rob Browning
2002-05-22  2:11   ` Thien-Thi Nguyen
2002-05-22  4:23     ` Rob Browning
2002-05-22  7:40       ` Thien-Thi Nguyen [this message]
2002-05-22 12:28 ` Marius Vollmer
2002-05-22 19:29   ` Thien-Thi Nguyen
2002-05-22 20:09     ` conversation via CVS Joshua Judson Rosen
2002-05-22 20:48       ` Thien-Thi Nguyen
2002-05-22 23:37         ` Joshua Judson Rosen
2002-05-22 23:43           ` Thien-Thi Nguyen
2002-05-23 11:47         ` MJ Ray
2002-05-22 20:54     ` updated $workbook/modules/modules-and-shared-libs.text Marius Vollmer
2002-05-22 22:27       ` Thien-Thi Nguyen

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=E17AQjk-0002P8-00@giblet \
    --to=ttn@giblet.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).