Subject: changes to rc
Date: Sun, 19 Sep 1993 09:32:06 -0400 [thread overview]
Message-ID: <9309192031.AA01761@netmail.microsoft.com> (raw)
Chris Siebenmann makes the very sane suggestion:
: the best way to persuade people that it's a good idea is to implement it
: in your version and then post the code so other people can try it out.
I agree wholeheartedly. We can argue 'til we're blue in the face about
this and other weeny details, and still not get anywhere. I've learned
that when things get into the blue-in-the-face stage, the way to settle
the argument is to *JUST DO IT*. Sometimes you win, sometimes you lose,
but at least you'll know your proposal got a fair shake.
ObRC: Hey Byron, how close are we to 1.5?
Raymond (not rc) Chen (email@example.com)
next reply other threads:[~1993-09-19 20:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-09-19 13:32 raymondc [this message]
-- strict thread matches above, loose matches on Subject: below --
1993-09-19 20:48 Byron Rakitzis
1993-09-17 19:50 Chris Siebenmann
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).