From: Greg KH <gregkh@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [GIT PATCH] driver core patches for 3.3-rc1
Date: Mon, 30 Jan 2012 13:14:56 -0800 [thread overview]
Message-ID: <20120130211456.GA13580@suse.de> (raw)
In-Reply-To: <CA+55aFxeFWnuywj2x5xzQhXg6NWQENpK=n=V1xHvMJZncFhYMQ@mail.gmail.com>
On Sat, Jan 28, 2012 at 06:22:41PM -0800, Linus Torvalds wrote:
> On Fri, Jan 27, 2012 at 3:09 PM, Greg KH <gregkh@suse.de> wrote:
> > 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? If
> > so, I'll go build 1.7.9 as I see that is now out today.
> >
> > Did I mess something up? I created the tag with:
> > git tag -u kroah.com -s driver-core-3.3-rc1-bugfixes driver-core-linus
>
> No, everything looks fine, and I just pulled it.
>
> But your old version of git won't be able to do that pull (or
> request-pull) since it doesn't have support for the signed tag
> feature. So the signed tag itself works fine, and I can pull from you,
> but yes, you need to have a newer version yourself to see how that
> works.
Ok, thanks for verifying that I didn't mess anything up on my side.
greg k-h
prev parent reply other threads:[~2012-01-30 21:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 23:09 [GIT PATCH] driver core patches for 3.3-rc1 Greg KH
2012-01-28 8:34 ` Junio C Hamano
2012-01-30 21:15 ` Greg KH
2012-01-29 2:22 ` Linus Torvalds
2012-01-30 21:14 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120130211456.GA13580@suse.de \
--to=gregkh@suse.de \
--cc=akpm@linux-foundation.org \
--cc=gitster@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).