From: Cort Dougan <cort@fsmlabs.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Grover, Andrew" <andrew.grover@intel.com>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: source control?
Date: Thu, 23 Aug 2001 21:22:49 -0600 [thread overview]
Message-ID: <20010823212249.N498@ftsoj.fsmlabs.com> (raw)
In-Reply-To: <4148FEAAD879D311AC5700A0C969E89006CDE0A4@orsmsx35.jf.intel.com> <E15a3tR-0004rN-00@the-village.bc.nu>
In-Reply-To: <E15a3tR-0004rN-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Fri, Aug 24, 2001 at 12:28:09AM +0100
That's a great description of all source control! "Makes it all to easy
for other people to push crap into your tree"!
There is great benefit to making it very hard for people to get changes
into a tree. It forces people to ask "Is this really worth all the
effort?" several times. It's a great filter.
} It does. Or at least many of the development teams do. That doesn't mean a
} general CVS is a good idea. CVS make it all to easy for other people to
} push crap into your tree.
next prev parent reply other threads:[~2001-08-24 3:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-23 21:29 source control? Grover, Andrew
2001-08-23 22:34 ` Nicholas Knight
2001-08-23 22:49 ` Larry McVoy
2001-08-23 23:28 ` Alan Cox
2001-08-24 3:22 ` Cort Dougan [this message]
2001-08-24 17:02 ` Florian Weimer
2001-08-24 10:29 ` Gérard Roudier
2001-08-24 12:16 ` Alan Cox
2001-08-24 13:15 ` Gérard Roudier
-- strict thread matches above, loose matches on Subject: below --
2001-08-24 12:53 Samium Gromoff
2001-08-24 13:25 Samium Gromoff
2001-08-24 17:20 Samium Gromoff
2001-08-24 17:25 ` Larry McVoy
2001-08-24 17:29 ` Florian Weimer
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=20010823212249.N498@ftsoj.fsmlabs.com \
--to=cort@fsmlabs.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrew.grover@intel.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