From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from zeniv.linux.org.uk ([195.92.253.2]:49802 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2994216AbcBSWWZ (ORCPT ); Fri, 19 Feb 2016 17:22:25 -0500 Date: Fri, 19 Feb 2016 22:22:21 +0000 From: Al Viro To: Mike Marshall Cc: Martin Brandenburg , Linus Torvalds , linux-fsdevel , Stephen Rothwell Subject: Re: Orangefs ABI documentation Message-ID: <20160219222221.GB17997@ZenIV.linux.org.uk> References: <20160218111122.GS17997@ZenIV.linux.org.uk> <20160218205206.GW17997@ZenIV.linux.org.uk> <20160219002539.GX17997@ZenIV.linux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Fri, Feb 19, 2016 at 05:11:29PM -0500, Mike Marshall wrote: > I plan to update the kernel.org orangefs for-next tree to look exactly > like the "current" branch of my github tree, unless someone says > not to: > > github.com/hubcapsc/linux/tree/current Latest commit c1223ca $ git checkout current $ git fetch git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git orangefs-untested $ git diff FETCH_HEAD # should report no differences $ git reset --hard FETCH_HEAD $ git push --force then push the same branch into your kernel.org (as for-next, again with -force).