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  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:   Sun, 26 May 2019 19:53:53 +0200
From:   Paolo Bonzini <>
To:     Linus Torvalds <>
Cc:     Linux List Kernel Mailing <>,
        Radim Krčmář <>,
        KVM list <>
Subject: Re: [GIT PULL] KVM changes for Linux 5.2-rc2

On 26/05/19 17:51, Linus Torvalds wrote:
> On Sun, May 26, 2019 at 2:56 AM Paolo Bonzini <> wrote:
>> tags/for-linus
> This says it's a tag, but it's not. It's just a commit pointer (also
> called a "lightweight tag", because while it technically is exactly
> the same thing as a branch, it's obviously in the tag namespace and
> git will _treat_ it like a tag).
> Normally your tags are proper signed tags. So I'm not pulling this,
> waiting for confirmation.

Shell history shows that I typed

	git push kvm +HEAD:tags/for-linus

(which matches the "git push kvm +HEAD:queue" that I often do, and
therefore can be explained by muscle memory).

The interesting thing is that not only git will treat lightweight tags
like, well, tags: in addition, because I _locally_ had a tag object that
pointed to the same commit and had the same name, git-request-pull
included my local tag's message in its output!  I wonder if this could
be considered a bug.

I have now pushed the actual tag object to the same place.


Powered by blists - more mailing lists