From: Aaron Lehmann <aaronl@vitelus.com>
To: linux-kernel@vger.kernel.org
Subject: BKCVS issue
Date: Mon, 2 Jun 2003 14:14:36 -0700 [thread overview]
Message-ID: <20030602211436.GF14878@vitelus.com> (raw)
For the past few days, it seems like every time something changes in
BK, the bkcvs repository has all of its files touched. At least, all
files in the repository have a P preceding their names on a cvs up.
It's not intolerable, but I was wondering if anyone's aware of it.
next reply other threads:[~2003-06-02 21:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-02 21:14 Aaron Lehmann [this message]
2003-06-02 23:37 ` BKCVS issue Rob Landley
2003-06-02 23:39 ` Ben Collins
2003-06-03 0:50 ` Rob Landley
2003-06-03 0:03 ` Ben Collins
2003-06-03 0:37 ` Aaron Lehmann
2003-06-03 2:28 ` Larry McVoy
2003-06-03 6:56 ` Jasper Spaans
2003-06-05 20:54 ` Larry McVoy
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=20030602211436.GF14878@vitelus.com \
--to=aaronl@vitelus.com \
--cc=linux-kernel@vger.kernel.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