All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: import of usb series failed
Date: Fri, 19 Feb 2010 07:53:43 -0800	[thread overview]
Message-ID: <20100219155343.GA3946@kroah.com> (raw)
In-Reply-To: <20100219175218.10025a7a.sfr@canb.auug.org.au>

On Fri, Feb 19, 2010 at 05:52:18PM +1100, Stephen Rothwell wrote:
> Hi Greg,
> 
> On Thu, 18 Feb 2010 13:22:21 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > On Wed, 17 Feb 2010 16:21:44 -0800 Greg KH <greg@kroah.com> wrote:
> > >
> > > Very wierd, you must have gotten this just as I updated my tree.  It
> > 
> > Yeah, that is possible.
> > 
> > > should all be fine tomorrow, if not, please let me know.
> > 
> > Great, thanks.
> 
> I got the same today.  Is this a case of Git being a bit more picky about
> applying patches that quilt?

Very wierd.  I just ran 'git quiltimport' on my whole tree onto Linus's
latest git tree and it worked just fine.

What is the command you are using here to do this?  Perhaps there is
some other tree modifying this file causing a problem?

odd,

greg k-h

  reply	other threads:[~2010-02-19 15:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-17 23:55 linux-next: import of usb series failed Stephen Rothwell
2010-02-18  0:21 ` Greg KH
2010-02-18  2:22   ` Stephen Rothwell
2010-02-19  6:52     ` Stephen Rothwell
2010-02-19 15:53       ` Greg KH [this message]
2010-02-20  1:02         ` Stephen Rothwell
2010-02-24  2:16           ` Greg KH
2010-02-24  4:01             ` Stephen Rothwell
2010-02-25 17:54               ` Greg KH
2010-02-26  0:27                 ` Stephen Rothwell

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=20100219155343.GA3946@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.