public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Felix Blyakher <felixb@sgi.com>,
	Lachlan McIlroy <lachlan@redback.melbourne.sgi.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	xfs mailing list <xfs@oss.sgi.com>
Subject: Re: [GIT PULL] XFS update for 2.6.30
Date: Fri, 3 Apr 2009 10:02:15 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.2.00.0904030954030.4130@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.00.0904030952220.4130@localhost.localdomain>



On Fri, 3 Apr 2009, Linus Torvalds wrote:

> 
> 
> On Thu, 2 Apr 2009, Felix Blyakher wrote:
> > 
> > Were there any problems pulling from the xfs repository?
> 
> Sorry, no - just too much email, too many trees to look at, too many 
> people to argue with.
> 
> Pulled.

Side note - I almost unpulled afterwards. 

You've done several apparently totally useless pulls from my tree at 
random points. 

Daily "keep up-to-date with Linus' tree" pulls are _strongly_ discouraged 
(read: if this continues, I'll just stop pulling from you), because it 
makes the history totally unreadable after-the-fact. It has some direct 
technical downsides (it makes it much harder to run "git bisect" and see 
what is going on), but apart from those direct downsides it just makes it 
much harder for me - or anybody else who wants to get an overview of what 
happened - to visualize things when history is messy.

Instead of having a clear nice line of development that says "this is what 
happened to XFS", those merges have basically mixed up all your changes 
with all the random _other_ changes in the tree. 

In other words, having those extra merges makes the graphical tools almost 
useless for getting some kind of "what happened" overview. 

I realize that an occasional back-merge may be required to resolve big 
conflicts early, but they really have to be pretty big and immediate for 
it to be a win. 

			Linus

  reply	other threads:[~2009-04-03 17:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-31  5:30 [GIT PULL] XFS update for 2.6.30 Felix Blyakher
2009-04-02 16:26 ` Felix Blyakher
2009-04-03 16:52   ` Linus Torvalds
2009-04-03 17:02     ` Linus Torvalds [this message]
2009-04-03 17:41       ` Felix Blyakher
2009-04-04  1:19         ` david
2009-04-04  1:54           ` Felix Blyakher
2009-04-14 14:44 ` XFS support for TRIM / blkdev_issue_discard? Peter Niemayer

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=alpine.LFD.2.00.0904030954030.4130@localhost.localdomain \
    --to=torvalds@linux-foundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=felixb@sgi.com \
    --cc=lachlan@redback.melbourne.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xfs@oss.sgi.com \
    /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