Skip to contentSkip to conversation

DISCUSSION [email protected] 1 participant 1 message May 24, 2005

lore
Share & tools
lore
#0 lore raw
	by smtp.nexlab.net (Postfix) with ESMTP id 7C555FB73

	for <[email protected]>; Tue, 24 May 2005 10:01:46 +0200 (CEST)

Received: ([email protected]) by vger.kernel.org via listexpand

	id S261416AbVEXHrr (ORCPT <rfc822;[email protected]>);

	Tue, 24 May 2005 03:47:47 -0400

Received: ([email protected]) by vger.kernel.org id S261414AbVEXHrr

	(ORCPT <rfc822;linux-kernel-outgoing>);

	Tue, 24 May 2005 03:47:47 -0400

Received: from fire.osdl.org ([65.172.181.4]:48015 "EHLO smtp.osdl.org")

	by vger.kernel.org with ESMTP id S261416AbVEXHrp (ORCPT

	<rfc822;[email protected]>);

	Tue, 24 May 2005 03:47:45 -0400

Received: from shell0.pdx.osdl.net (fw.osdl.org [65.172.181.6])

	by smtp.osdl.org (8.12.8/8.12.8) with ESMTP id j4O7iVjA029720

	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);

	Tue, 24 May 2005 00:44:31 -0700

Received: from localhost (shell0.pdx.osdl.net [10.9.0.31])

	by shell0.pdx.osdl.net (8.13.1/8.11.6) with ESMTP id j4O7iUjI014722;

	Tue, 24 May 2005 00:44:30 -0700

Date: Tue, 24 May 2005 00:46:35 -0700 (PDT)

From: Linus Torvalds <[email protected]>
To: Jeff Garzik <[email protected]>
Cc: Andrew Morton <[email protected]>, Netdev <[email protected]>,
Linux Kernel <[email protected]>
Subject: Re: [git patches] 2.6.x net driver updates

In-Reply-To: <[email protected]>

Message-ID: <[email protected]>

References: <[email protected]> <[email protected]>

<[email protected]> <[email protected]>

<[email protected]>

MIME-Version: 1.0

Content-Type: TEXT/PLAIN; charset=US-ASCII

X-Spam-Status: No, hits=0 required=5 tests=

X-Spam-Checker-Version: SpamAssassin 2.63-osdl_revision__1.40__

X-MIMEDefang-Filter: osdl$Revision: 1.109 $

X-Scanned-By: MIMEDefang 2.36

Sender: [email protected]
Precedence: bulk

X-Mailing-List: [email protected]

Quoted 5 lines · Jeff Garzik

Ok, I'll fix the commit message.

As for different trees, I'm afraid you've written something that is _too useful_ to be used in that manner.

I really think you'll eventually confuse yourself terminally, but as long as the commit messages end up being meaningful, your "mush everything together" clearly is the thing that is going to perform best.

Quoted 3 lines

Git has brought with it a _major_ increase in my productivity because I can now easily share ~50 branches with 50 different kernel hackers, without spending all day running rsync.

Hey, I'm happy it works for you, but are you sure those 50 other kernel hackers aren't confused?

IOW, your work model is pretty extreme, and I'm much more worried about mixing up trees by mistake than about the technical side of git per se. That's also why I think it's important that the commit logs are
meaningful: they do end up containing the SHA1 key, so clearly "all the information" is there, but if something gets mixed up, I'd like some human to be able to eventualyl say "Aaahhh.. _that's_ where it got mixed up".

Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/