From: Larry McVoy <lm@bitmover.com>
To: Anders Gustafsson <andersg@0x63.nu>
Cc: Larry McVoy <lm@bitmover.com>,
Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>,
Carl Gherardi <C.Gherardi@curtin.edu.au>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.5.59
Date: Thu, 16 Jan 2003 20:25:41 -0800 [thread overview]
Message-ID: <20030117042541.GC15753@work.bitmover.com> (raw)
In-Reply-To: <20030117042041.GC1794@h55p111.delphi.afb.lu.se>
> Whats the difference between bk co and bk get?
co has RCS compat options and get has SCCS compat options. If you are
used to CVS/RCS, "bk co" and "bk ci" are your friend, if you are used
to SCCS then "bk get" and "bk delta" are what you like. They do the
same thing.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2003-01-17 4:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 4:06 Linux 2.5.59 Carl Gherardi
2003-01-17 4:08 ` Randy.Dunlap
2003-01-17 4:12 ` Kai Germaschewski
2003-01-17 4:16 ` Anders Gustafsson
2003-01-17 4:18 ` Larry McVoy
2003-01-17 4:24 ` Kai Germaschewski
2003-01-17 12:28 ` Geert Uytterhoeven
2003-01-17 16:36 ` Kai Germaschewski
2003-01-17 20:07 ` Sam Ravnborg
2003-01-17 4:17 ` Larry McVoy
2003-01-17 4:20 ` Anders Gustafsson
2003-01-17 4:25 ` Larry McVoy [this message]
2003-01-17 5:00 ` Michael D. Shannon
2003-01-17 4:41 ` Joshua Kwan
2003-01-17 9:30 ` David Woodhouse
2003-01-17 4:21 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2003-01-17 2:28 Linus Torvalds
2003-01-17 4:44 ` William Lee Irwin III
2003-01-17 7:15 ` Udo A. Steinberg
2003-01-17 7:30 ` Udo A. Steinberg
2003-01-17 9:59 ` Adrian Bunk
2003-01-17 10:23 ` Marc Zyngier
2003-01-17 11:37 ` Adrian Bunk
2003-01-17 16:55 ` John Cherry
2003-01-17 17:10 ` Russell King
2003-01-17 17:10 ` Martin J. Bligh
2003-01-18 4:03 ` Ernst Herzberg
2003-01-20 9:54 ` Christoph Hellwig
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=20030117042541.GC15753@work.bitmover.com \
--to=lm@bitmover.com \
--cc=C.Gherardi@curtin.edu.au \
--cc=andersg@0x63.nu \
--cc=kai@tp1.ruhr-uni-bochum.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.