From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: guile-devel@gnu.org
Subject: Re: using guile scripts from hack/scripts
Date: Wed, 03 Apr 2002 02:52:57 -0800 [thread overview]
Message-ID: <E16siNt-0002lD-00@giblet> (raw)
In-Reply-To: <m3ofh3wje0.fsf@laruns.ossau.uklinux.net> (message from Neil Jerram on 01 Apr 2002 16:03:51 +0100)
From: Neil Jerram <neil@ossau.uklinux.net>
Date: 01 Apr 2002 16:03:51 +0100
I must remember to add lint to unstable sometime. (Unless someone
does it for me.)
sorry i didn't give you this tip when suggesting you to add lint: when
doing changes that apply to multiple branches i try to start w/ HEAD and
go back from there (most applicable for new stuff). this is easier than
adding at (say) 1.6 and trying to figure out the situation both forward
(HEAD) and backward (1.4).
thi
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2002-04-03 10:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-31 21:15 using guile scripts from hack/scripts Thien-Thi Nguyen
2002-04-01 15:03 ` Neil Jerram
2002-04-03 10:52 ` Thien-Thi Nguyen [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=E16siNt-0002lD-00@giblet \
--to=ttn@giblet.glug.org \
--cc=guile-devel@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).