From: "David S. Miller" <davem@redhat.com>
To: bruce@cenderis.demon.co.uk
Cc: gcc@gnu.org
Subject: Re: source mgt. requirements solicitation
Date: Sun, 08 Dec 2002 16:52:00 -0000 [thread overview]
Message-ID: <20021208.164551.82192634.davem@redhat.com> (raw)
In-Reply-To: <87isy4m7hp.fsf@cenderis.demon.co.uk>
From: Bruce Stephens <bruce@cenderis.demon.co.uk>
Date: Sun, 08 Dec 2002 23:11:14 +0000
However, that's an interesting point: what do you do with CVS and with
BitKeeper? What operations are performance-critical for you?
I think CVS's weak performance points are so well understood
by other people that they can comment as good as or better
than me :-)
Operations on a branch are painful, so someone can start there :-)
next prev parent reply other threads:[~2002-12-09 0:49 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-08 7:13 on reputation and lines and putting things places (Re: gcc branches?) Robert Dewar
2002-12-08 14:18 ` source mgt. requirements solicitation Tom Lord
2002-12-08 14:56 ` DJ Delorie
2002-12-08 15:02 ` David S. Miller
2002-12-08 15:45 ` Bruce Stephens
2002-12-08 16:52 ` David S. Miller [this message]
2002-12-08 15:11 ` Bruce Stephens
2002-12-08 16:24 ` Joseph S. Myers
2002-12-08 16:47 ` Tom Lord
2002-12-08 22:20 ` Craig Rodrigues
2002-12-08 16:09 ` Phil Edwards
2002-12-08 19:13 ` Zack Weinberg
2002-12-09 10:33 ` Phil Edwards
2002-12-09 11:06 ` Joseph S. Myers
2002-12-09 9:42 ` Zack Weinberg
2002-12-09 11:00 ` Jack Lloyd
2002-12-09 15:10 ` Walter Landry
2002-12-09 15:27 ` Joseph S. Myers
2002-12-09 17:05 ` Walter Landry
2002-12-09 17:10 ` Joseph S. Myers
2002-12-09 18:27 ` Walter Landry
2002-12-09 19:16 ` Joseph S. Myers
2002-12-10 0:27 ` Zack Weinberg
2002-12-10 0:41 ` Tom Lord
2002-12-10 12:05 ` Phil Edwards
2002-12-10 19:44 ` Mark Mielke
2002-12-10 19:57 ` David S. Miller
2002-12-10 20:02 ` Phil Edwards
2002-12-10 23:07 ` David S. Miller
2002-12-11 6:31 ` Phil Edwards
2002-12-14 13:43 ` Linus Torvalds
2002-12-14 14:06 ` Tom Lord
2002-12-14 17:44 ` Linus Torvalds
2002-12-14 19:45 ` Tom Lord
2002-12-14 14:41 ` Neil Booth
2002-12-14 15:47 ` Zack Weinberg
2002-12-14 15:33 ` Momchil Velikov
2002-12-14 16:06 ` Linus Torvalds
2002-12-15 3:59 ` Momchil Velikov
2002-12-15 8:26 ` Momchil Velikov
2002-12-15 12:02 ` Linus Torvalds
2002-12-15 14:16 ` Momchil Velikov
2002-12-15 15:20 ` Pop Sébastian
2002-12-15 16:09 ` Linus Torvalds
2002-12-15 16:49 ` Bruce Stephens
2002-12-15 16:59 ` Linus Torvalds
2002-12-15 18:10 ` Bruce Stephens
2002-12-16 8:32 ` Diego Novillo
2002-12-17 3:36 ` Pop Sébastian
2002-12-17 13:14 ` Tom Lord
2002-12-17 15:28 ` Itching and scratching (Re: source mgt. requirements solicitation) Stan Shebs
2002-12-17 16:07 ` Tom Lord
2002-12-17 15:46 ` Stan Shebs
2002-12-16 17:22 ` source mgt. requirements solicitation Mike Stump
2002-12-15 17:09 ` Stan Shebs
2002-12-09 17:50 ` Zack Weinberg
2002-12-11 1:11 ` Branko Čibej
2002-12-08 18:32 ` Joseph S. Myers
2002-12-11 2:48 ` Branko Čibej
2002-12-12 6:43 Robert Dewar
2002-12-14 20:16 Nathanael Nerode
2002-12-14 21:34 ` Linus Torvalds
2002-12-15 18:29 Nathanael Nerode
2002-12-18 9:06 Robert Dewar
2002-12-18 9:07 Robert Dewar
2002-12-18 9:48 ` Linus Torvalds
2002-12-18 10:11 ` Phil Edwards
2002-12-18 9:22 Robert Dewar
2002-12-18 9:35 Robert Dewar
2002-12-18 9:58 Robert Dewar
2002-12-18 17:33 Robert Dewar
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=20021208.164551.82192634.davem@redhat.com \
--to=davem@redhat.com \
--cc=bruce@cenderis.demon.co.uk \
--cc=gcc@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).