Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753740AbaA3SXJ (ORCPT ); Thu, 30 Jan 2014 13:23:09 -0500 Received: from mail-ve0-f174.google.com ([209.85.128.174]:39276 "EHLO mail-ve0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752728AbaA3SXH (ORCPT ); Thu, 30 Jan 2014 13:23:07 -0500 MIME-Version: 1.0 In-Reply-To: <20140129185449.GC30065@fieldses.org> References: <20140129185449.GC30065@fieldses.org> Date: Thu, 30 Jan 2014 10:23:06 -0800 X-Google-Sender-Auth: ECy8RiPh5NfO4n6tKzjNeX4Ih0U Message-ID: Subject: Re: please pull nfsd changes for 3.14 From: Linus Torvalds To: "J. Bruce Fields" Cc: Linux NFS Mailing List , Linux Kernel Mailing List Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 29, 2014 at 10:54 AM, J. Bruce Fields wrote: > > Stephen Rothwell noted a merge conflict: > > http://marc.info/?i=<20140129124238.6e1667abab08be8be2dafe01@canb.auug.org.au> > > I'm assuming as usual you'll handle it and let me know if you need > anything from me. Heh. The conflict was trivial, and git does 99% of it automatically - leaving just the header file inclusions to be resolved manually because they were right next to each other. The resolution just looks scarier than it is because there were other changes that did resolve cleanly, but that were "close enough" to each other that the context overlapped, so they are shown too.. But yes, had it actually been complicated, I'd probably still have done it, and perhaps asked you to verify it. We did have a couple of more serious conflicts in this merge window. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/