All of lore.kernel.org
 help / color / mirror / Atom feed
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, linux-serial@vger.kernel.org
Subject: Re: [GIT PATCH] TTY/serial patches for 3.3-rc1
Date: Mon, 30 Jan 2012 16:13:08 -0800	[thread overview]
Message-ID: <20120131001308.GB20588@suse.de> (raw)
In-Reply-To: <CA+55aFxGf8-Bv8Jrhm1dbTg6AkTi37Vfuw5OOC7hDokKRa4hjw@mail.gmail.com>

On Mon, Jan 30, 2012 at 03:20:52PM -0800, Linus Torvalds wrote:
> On Mon, Jan 30, 2012 at 3:19 PM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > Tssk. Your script is broken, or your manual fixup is broken. Look at
> > the tag-name again.
> >
> > I pulled the correct one, but please be more careful.
> 
> Oh, and if it's because your old script can't verify the tag-names, so
> you fix things up by hand instead of scripting it, try using
> "tags/<tagname>" instead of just "<tagname>". That makes old git
> versions at least see the reference, even if they don't then react to
> the signing itself (ie they just treat it as the commit it points to,
> rather than as a tag with interesting contents in itself)

Ah, ok, I'll try that out.

Or I can spend the time to get the new version of git installed.
Wrestling with my scripts or rpm, I don't know which is worse...

greg k-h

  reply	other threads:[~2012-01-31  0:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-30 21:12 [GIT PATCH] TTY/serial patches for 3.3-rc1 Greg KH
2012-01-30 23:19 ` Linus Torvalds
2012-01-30 23:19   ` Linus Torvalds
2012-01-30 23:20   ` Linus Torvalds
2012-01-31  0:13     ` Greg KH [this message]
2012-01-31  0:27       ` Linus Torvalds
2012-01-31  1:11         ` Greg KH
2012-01-31  0:12   ` Greg KH
2012-01-31  0:12     ` 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=20120131001308.GB20588@suse.de \
    --to=gregkh@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.