From: Tim Goodwin <tjg@star.le.ac.uk>
To: quanstro@quanstro.net
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: -V ?
Date: Tue, 19 Jun 2001 05:01:01 -0500 [thread overview]
Message-ID: <20010619090101.24010.qmail@happy.star.le.ac.uk> (raw)
In-Reply-To: <20010618182740.7F6FF3EA0A@quanstro.net>
> the NEWS file claims a -V option, which doesn't seem to
> exist in main.c
Ah, hmm, well.
I haven't updated the NEWS file since the 1.6 release; it still
describes changes since 1.4. This is an oversight, rather than a
deliberate policy! I've scratched the file, and started again with
major changes since the 1.6 release (of which there aren't all that
many). So in the next snapshot / beta, NEWS will be relevant again.
As to the `-V' flag, I replaced it with the `$version' variable. This
makes it easy to find the version of the current rc, which you
couldn't do with the `-V' flag, and you can always say
rc -c 'whatis version'
to get the effect of the old `-V'.
Tim.
prev parent reply other threads:[~2001-06-19 21:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-18 19:27 erik quanstrom
2001-06-19 10:01 ` Tim Goodwin [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010619090101.24010.qmail@happy.star.le.ac.uk \
--to=tjg@star.le.ac.uk \
--cc=quanstro@quanstro.net \
--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).