public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: lewis@sistina.com,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [repost] Announce: Linux-OpenLVM mailing list
Date: Thu, 19 Apr 2001 18:36:19 -0700	[thread overview]
Message-ID: <3ADF9293.E5375BB3@kegel.com> (raw)

Dear Sistina:

I know very little about LVM, but from watching earlier projects
in the same situation you're in now, the path you need to follow
seems clear:
   Stop using CVS internally for development.
   It makes checking in changes without submitting them to 
   Linus too easy.

To get sync'd back up, *start with the standard kernel*,
and start generating clean, human-understandable patches one 
at a time that bring it up to where you want.

Once you've achieved that, have your programmers generate patches 
rather than checking in to CVS, and feed the patches to Linus 
at the same time you hand them out to your other programmers.
Individual programmers may need to do more testing this way, but
c'est la vie.

This is the only way to achieve union with the standard kernel.

So many projects have failed to learn this lesson...
ignore it at your peril.
- Dan

             reply	other threads:[~2001-04-20  1:36 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-20  1:36 Dan Kegel [this message]
     [not found] <20010419144815.J10345@sistina.com>
2001-04-20 19:24 ` [repost] Announce: Linux-OpenLVM mailing list Heinz J. Mauelshagen
2001-04-20 18:04   ` Alan Cox
2001-04-20 18:25     ` Jens Axboe
2001-04-23 10:16       ` Heinz J. Mauelshagen
2001-04-23  9:50     ` Heinz J. Mauelshagen
  -- strict thread matches above, loose matches on Subject: below --
2001-04-20  9:33 Constantine Gavrilov
2001-04-19 17:51 Jes Sorensen
2001-04-19 18:29 ` AJ Lewis
2001-04-19 18:34   ` Jeff Garzik
2001-04-19 18:35   ` Rik van Riel
2001-04-24 14:58     ` Heinz J. Mauelshagen
2001-04-19 18:48   ` Jens Axboe
2001-04-24 14:54     ` Heinz J. Mauelshagen
2001-04-19 19:02   ` Alan Cox
2001-04-19 19:24     ` AJ Lewis
2001-04-19 19:33       ` Jens Axboe
2001-04-19 19:46         ` Martin K. Petersen
2001-04-24 15:00           ` Heinz J. Mauelshagen
2001-04-19 19:35       ` Jes Sorensen
2001-04-19 19:44         ` AJ Lewis
2001-04-19 20:33       ` Miles Lane
2001-04-20 12:36         ` Doug McNaught
2001-04-20 22:55           ` Matti Aarnio
2001-04-21 20:45             ` Rik van Riel
2001-04-19 19:17   ` Jes Sorensen
2001-04-19 19:26     ` AJ Lewis
2001-04-19 19:40       ` Jes Sorensen
2001-04-19 19:19   ` Martin K. Petersen

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=3ADF9293.E5375BB3@kegel.com \
    --to=dank@kegel.com \
    --cc=lewis@sistina.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