netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>, Netdev <netdev@oss.sgi.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [git patches] 2.6.x net driver updates
Date: Tue, 24 May 2005 03:29:37 -0400	[thread overview]
Message-ID: <4292D7E1.80601@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0505232343260.2307@ppc970.osdl.org>

Linus Torvalds wrote:
> 
> On Tue, 24 May 2005, Jeff Garzik wrote:
> 
>>You are getting precisely the same thing you got under BitKeeper:  pull 
>>from X, you get my tree, which was composed from $N repositories.  The 
>>tree you pull was created by my running 'bk pull' locally $N times.
> 
> 
> No. Under BK, you had DIFFERENT TREES.
> 
> What does that mean? They had DIFFERENT NAMES.
> 
> Which meant that the commit message was MEANINGFUL.

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.

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.  Suddenly my kernel development 
is a whole lot more _open_ to the world, with a single "./push".  And 
it's awesome.

That wasn't possible before with BitKeeper, just due to sheer network 
overhead of 50 trees.  With BitKeeper, the _only_ thing that kernel 
hackers and users could get from me is a mush tree with everything 
merged into a big 'ALL' repository.

So I'll continue to be the oddball, because more people can work in 
parallel with me that way.  I'll just have to make sure the commit 
messages look right to you.

	Jeff

  reply	other threads:[~2005-05-24  7:29 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4292BA66.8070806@pobox.com>
2005-05-24  6:08 ` [git patches] 2.6.x net driver updates Linus Torvalds
2005-05-24  6:25   ` Jeff Garzik
2005-05-24  6:48     ` Linus Torvalds
2005-05-24  7:29       ` Jeff Garzik [this message]
2005-05-24  7:46         ` Linus Torvalds
2005-05-24  7:55         ` David Lang
2005-05-24  6:34   ` Jeff Garzik
2005-05-24  6:50     ` Linus Torvalds
     [not found] <42B456E2.8000500@pobox.com>
2005-06-18 17:51 ` Linus Torvalds
2005-06-18 18:06   ` Linus Torvalds
2005-06-18 18:24     ` Linus Torvalds
2005-06-18 18:36       ` Jeff Garzik
2005-06-18 18:48         ` Linus Torvalds
2005-06-18 20:04           ` Jeff Garzik
2005-06-18 20:23             ` Linus Torvalds
2005-10-28  0:42 Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2005-10-29 18:21 Jeff Garzik
2005-11-05 19:58 Jeff Garzik
2005-11-09  6:53 Jeff Garzik
2006-01-03 16:41 Jeff Garzik
2006-01-09 17:10 Jeff Garzik
2006-01-12 22:13 Jeff Garzik
2006-01-12 22:30 ` Linus Torvalds
2006-01-12 22:39   ` Andrew Morton
2006-01-12 22:46     ` Linus Torvalds
2006-01-13 17:56       ` Roman Zippel
2006-01-13 19:23     ` Jens Axboe
2006-01-13 19:28       ` Sam Ravnborg
2006-01-13 19:36         ` Jens Axboe
2006-01-14  2:29         ` Adrian Bunk
2006-01-14  5:05           ` Randy.Dunlap
2006-01-12 22:42   ` Jeff Garzik
2006-01-12 23:14     ` Adrian Bunk

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=4292D7E1.80601@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=torvalds@osdl.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 NNTP newsgroup(s).