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 02:25:51 -0400	[thread overview]
Message-ID: <4292C8EF.3090307@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0505232253160.2307@ppc970.osdl.org>

Linus Torvalds wrote:
> 
> On Tue, 24 May 2005, Jeff Garzik wrote:
> 
> 
>>Please pull the 'for-linus' branch from
>>
>>rsync://rsync.kernel.org/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git
> 
> 
> Is this really what you meant to do? There's seven merges there, none of
> which have _any_ information about _what_ you merged, because you've mixed
> everything up in one tree, so that there's absolutely no record of the
> fact that you actually had seven different repositories that you pulled..
> 
> That sucks, Jeff.
> 
> I don't understand why you don't use different trees, like you did with
> BK. You can share the object directory with the different trees, but the
> way you work now, it all looks like mush.
> 
> Even if you don't get confused youself, you sure are confusing everybody 
> else with it..

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.

Ultimately, you appear to be complaining about:

* your own git-pull-script, which doesn't record the $2 (branch) 
argument in the commit message.

* the fact that my changelog includes the merge csets that were 
present-but-invisible by my BitKeeper submissions.  i.e. I lack a 
shortlog that filters out merge csets.



> Anyway, if you really want to work this way, with one big mushed-together
> thing that has different heads that you keep track of, can you _please_ at
> least make the commit message tell what you're doing. It's not a complex 

Hey, I didn't write git-pull-script, I just use it :)


> script, and you're definitely mis-using it as things stand now by 
> switching heads around inside one repository, and not telling other people 
> about it.

Switching heads around?  It sounds like you did not pull from the branch 
I mentioned.  This is how git-pull-script pulls from a branch:

git-pull-script \
rsync://rsync.kernel.org/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git\
  refs/heads/for-linus

	Jeff

  reply	other threads:[~2005-05-24  6:25 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 [this message]
2005-05-24  6:48     ` Linus Torvalds
2005-05-24  7:29       ` Jeff Garzik
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=4292C8EF.3090307@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).