linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Junio C Hamano <junio@pobox.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT PATCH] driver core patches for 3.3-rc1
Date: Mon, 30 Jan 2012 13:15:50 -0800	[thread overview]
Message-ID: <20120130211550.GB13580@suse.de> (raw)
In-Reply-To: <7v7h0cxm1j.fsf@alter.siamese.dyndns.org>

On Sat, Jan 28, 2012 at 12:34:48AM -0800, Junio C Hamano wrote:
> Greg KH <gregkh@suse.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 ;-).

Heh, fair enough :)

> 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.

As most of us used our own scripts for this, that makes sense, nice to
see it cleaned up a lot, I'll use it for my requests after I get 1.7.9
installed on my systems...

greg k-h

  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 [this message]
2012-01-29  2:22 ` Linus Torvalds
2012-01-30 21:14   ` Greg KH

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=20120130211550.GB13580@suse.de \
    --to=gregkh@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=junio@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).