linux-kernel - Re: [git pull] vfs.git regression fix

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 15 Jan 2016 13:08:44 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Al Viro <viro@...iv.linux.org.uk>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: [git pull] vfs.git regression fix

On Fri, Jan 15, 2016 at 1:00 PM, Al Viro <viro@...iv.linux.org.uk> 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