From: Carlo Strozzi <carlos@scriptaworks.com>
To: rc@hawkwind.utcs.toronto.edu
Subject: Re: rc 1.6 $version
Date: Sun, 31 Mar 2002 10:13:58 -0500 [thread overview]
Message-ID: <20020331171358.A604@strozzi.it> (raw)
In-Reply-To: <8ZFwtjf51i@dmul.paulhaahr.com>; from paul@paulhaahr.com on Sat, Mar 30, 2002 at 01:43:31PM -0500
On Sat, Mar 30, 2002 at 01:43:31PM -0500, Paul Haahr wrote:
>
> Why not just initialize version (provided there's none set in the
> environment?), not export it, and have any assignments turn it into a
> normal variable. I think that's pretty easy to do.
This certainly makes sense, I agree. Just forget about my proposed
special `rc_' namespace.
-cs-
--
For easier reading please set the Courier font.
Messages larger than 30 KB may not receive immediate attention.
Freedom for Business: http://swpat.ffii.org
next prev parent reply other threads:[~2002-04-03 20:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-14 22:37 erik quanstrom
2002-03-27 13:27 ` Tim Goodwin
2002-03-27 21:12 ` Carlo Strozzi
2002-03-30 18:43 ` Paul Haahr
2002-03-31 15:13 ` Carlo Strozzi [this message]
2002-04-03 14:31 ` Tim Goodwin
2002-04-03 15:06 ` Paul Haahr
2002-04-04 10:04 ` Tim Goodwin
2002-04-04 21:42 ` Scott Schwartz
2002-04-04 21:54 Byron Rakitzis
2002-04-05 8:35 ` Tim Goodwin
2002-04-05 1:38 Smarasderagd
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020331171358.A604@strozzi.it \
--to=carlos@scriptaworks.com \
--cc=rc@hawkwind.utcs.toronto.edu \
/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 NNTP newsgroup(s).