linux-kernel - Re: [GIT PATCH] driver core patches for 3.3-rc1

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 for Android: free password hash cracker in your pocket

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

Message-ID: <7v7h0cxm1j.fsf@alter.siamese.dyndns.org>
Date:	Sat, 28 Jan 2012 00:34:48 -0800
From:	Junio C Hamano <junio@...ox.com>
To:	Greg KH <gregkh@...e.de>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [GIT PATCH] driver core patches for 3.3-rc1

Greg KH <gregkh@...e.de> writes:

> I tried to create a signed tag for this pull request.  It's call
> "driver-core-3.3-rc1-bugfixes" in the repo below, but when I did:
>     git request-pull master git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/ driver-core-3.3-rc1-bugfixes > msg.txt
>
> I got the text below, no signed tag with the wording that I added to it
> that I could see.  Now I am still using git 1.7.8.3, is that why?

Ehh, the older versions never expected people to ask a tag to be pulled in
the first place, so there is no way they would have known to unwrap the
tag and pasted its tag message in the output ;-).

The request-pull script in 1.7.9 has finally received some belated
love. Since mid 2009, it didn't get much updates that improve the user
visible experience.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/