From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751789AbcAOVIq (ORCPT ); Fri, 15 Jan 2016 16:08:46 -0500 Received: from mail-io0-f176.google.com ([209.85.223.176]:35909 "EHLO mail-io0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750780AbcAOVIp (ORCPT ); Fri, 15 Jan 2016 16:08:45 -0500 MIME-Version: 1.0 In-Reply-To: <20160115210046.GG17997@ZenIV.linux.org.uk> References: <20160115201810.GF17997@ZenIV.linux.org.uk> <20160115210046.GG17997@ZenIV.linux.org.uk> Date: Fri, 15 Jan 2016 13:08:44 -0800 X-Google-Sender-Auth: tEz07gLRpxxvePwTiPvWN4sS3oA Message-ID: Subject: Re: [git pull] vfs.git regression fix From: Linus Torvalds To: Al Viro Cc: Linux Kernel Mailing List , linux-fsdevel 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 Fri, Jan 15, 2016 at 1:00 PM, Al Viro wrote: > > Buggy scripts, actually. The thing that generates them takes a branch > name as argument; turns out that it (pretty much by accident) treats the > missing argument as HEAD. Which tends to give reasonable diffstat and > shortlog, so I hadn't spotted the missing check until now. You could try "git request-pull". It _used_ to have somewhat similar issues, especially when the local branch had not made it to the remote point yet, but it should be good now. It actually warns if the remote name you give doesn't contain what the local branch contanis etc. > Fixed. BTW, is there any better way to get the current branch name than > git branch |sed -ne '/\* /s///p'? "git symbolic-ref HEAD" will show what HEAD points to. That's probably what you'd want.. Not that there is anything *wrong* with looking at "git branch" output, but that's really meant to be more human-readable than for scripting. Linus