linux-cvs
[Top] [All Lists]

Re: CVS Update@oss.sgi.com: performer

To: "Kevin D. Kissell" <kevink@mips.com>
Subject: Re: CVS Update@oss.sgi.com: performer
From: Ralf Baechle <ralf@oss.sgi.com>
Date: Tue, 21 Nov 2000 23:31:01 +0100
Cc: Tom Flyn <flynnt@oss.sgi.com>, linux-cvs@oss.sgi.com
In-reply-to: <019001c05405$e32fbc60$0deca8c0@Ulysses>; from kevink@mips.com on Tue, Nov 21, 2000 at 10:56:13PM +0100
References: <20001121212253Z553861-492+1011@oss.sgi.com> <019001c05405$e32fbc60$0deca8c0@Ulysses>
Sender: owner-linux-cvs@oss.sgi.com
On Tue, Nov 21, 2000 at 10:56:13PM +0100, Kevin D. Kissell wrote:

> Instead of sending us 102 distinct CVS update messages
> when a new subsystem is checked in for the first time,
> wouldn't it be possible (and kinder) to do a "cvs commit" of
> the whole set of files at one go?

Being as smart as CVS (read: as intelligent as a dead tree as long there's
some worms in it ;-) is it sends one mail per newly created directory in
the repository.

The real bug is that these messages should never have reached this list,
only changes to certain modules should go via this list.

  Ralf

<Prev in Thread] Current Thread [Next in Thread>