From: Aaron Lehmann <aaronl@vitelus.com>
To: Larry McVoy <lm@work.bitmover.com>, linux-kernel@vger.kernel.org
Subject: Re: *sigh* something is wrong with bkcvs again
Date: Sun, 24 Aug 2003 23:16:15 -0700 [thread overview]
Message-ID: <20030825061615.GJ31894@vitelus.com> (raw)
In-Reply-To: <20030823191458.GA25535@work.bitmover.com>
On Sat, Aug 23, 2003 at 12:14:58PM -0700, Larry McVoy wrote:
> Maybe you didn't intend it to sound like that and you'd like to rephrase it.
Hi Larry,
The disrespect wasn't directed towards you, but at the problem. BKcvs
is a great resource, but it's got some recurring bugs, and they're
quite frustrating. While I realize you're the author, everyone makes
mistakes. Your work on the CVS gateway is appreciated, even though it
isn't flawless yet.
prev parent reply other threads:[~2003-08-25 6:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-23 1:27 *sigh* something is wrong with bkcvs again Aaron Lehmann
2003-08-23 19:14 ` Larry McVoy
2003-08-24 0:13 ` Ken Moffat
2003-08-24 1:01 ` Larry McVoy
2003-08-24 10:27 ` Stephan von Krawczynski
2003-08-25 6:16 ` Aaron Lehmann [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=20030825061615.GJ31894@vitelus.com \
--to=aaronl@vitelus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@work.bitmover.com \
/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