xfs
[Top] [All Lists]

Re: [PATCH 0/2, RESEND] [XFS] a couple of fixes

To: Felix Blyakher <felixb@xxxxxxx>
Subject: Re: [PATCH 0/2, RESEND] [XFS] a couple of fixes
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Wed, 8 Apr 2009 09:33:50 -0400
Cc: Christoph Hellwig <hch@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
In-reply-to: <09C35383-EA8E-4EC2-A067-B3FA327AFF4C@xxxxxxx>
References: <1237116342-25701-1-git-send-email-david@xxxxxxxxxxxxx> <20090406222831.GA12016@xxxxxxxxxxxxx> <09C35383-EA8E-4EC2-A067-B3FA327AFF4C@xxxxxxx>
User-agent: Mutt/1.5.18 (2008-05-17)
On Tue, Apr 07, 2009 at 11:45:33PM -0500, Felix Blyakher wrote:
>
> On Apr 6, 2009, at 5:28 PM, Christoph Hellwig wrote:
>
>> I've sucked these patches into my tree after reviewin and QAing them.
>> Felix, can you pull this and send it to Linus for 2.6.30?
>>
>>      git://git.kernel.org/pub/scm/fs/xfs/xfs.git
>
> I did pull from your tree, and pushed to oss.
> But I stopped short from pushing the for-linus branch,
> and generating the pull request, as I'm again seeing
> the 'merge' commits. I'll try to sort it out tomorrow.

Note that you will always see some merge commits of both merged trees
touched the same files.  What Linus objected was the large amount of
merge commits.  The way to bring them down is to simply do less merges,
just stay on the same mainline level for a longer time and only merge
with mainline short before you prepare a pull or when you really need it
due to conflicting changes making it in.

<Prev in Thread] Current Thread [Next in Thread>