From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from zeniv.linux.org.uk ([195.92.253.2]:42504 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751474AbcCZOrD (ORCPT ); Sat, 26 Mar 2016 10:47:03 -0400 Date: Sat, 26 Mar 2016 14:47:00 +0000 From: Al Viro To: Mike Marshall Cc: Linus Torvalds , Martin Brandenburg , linux-fsdevel Subject: Re: Orangefs, v4.5 and the merge window... Message-ID: <20160326144700.GP17997@ZenIV.linux.org.uk> References: <20160311214745.GT17997@ZenIV.linux.org.uk> <20160326002116.GK17997@ZenIV.linux.org.uk> <20160326010140.GN17997@ZenIV.linux.org.uk> <20160326043041.GO17997@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 Sat, Mar 26, 2016 at 08:07:58AM -0400, Mike Marshall wrote: > Yay, Al, that did it, thanks! > > I've tested, and updated the for-next branch at kernel.org... > > Linus, if it is not too late, can you pull from: > > git://git.kernel.org/pub/scm/linux/kernel/git/hubcap/linux.git > for-next Shortlog and diffstat would be a good idea... Something like the output of git request-pull origin git://git.kernel.org/pub/scm/linux/kernel/git/hubcap/linux.git for-next Longer term you want a remote to avoid typing that crap every time; just be careful to set both url (git:// one) and pushurl (ssh:// equivalent) for it. The former will be usable for somebody to pull from you (and go into the output of git request-pull), the latter is obviously for pushes...