linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Greg KH <greg@kroah.com>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
	linux-next@vger.kernel.org, Kay Sievers <kay.sievers@vrfy.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: linux-next: pci/driver-core merge conflicts
Date: Fri, 30 May 2008 10:55:09 +1000	[thread overview]
Message-ID: <20080530105509.34faa639.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20080529160221.GA9876@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 669 bytes --]

On Thu, 29 May 2008 09:02:21 -0700 Greg KH <greg@kroah.com> wrote:
>
> On Thu, May 29, 2008 at 08:57:16AM -0700, Jesse Barnes wrote:
> > 
> > Hm, I knew this would cause problems eventually. :)  Should I put these fixups 
> > in my tree?  Or can you track them somehow, Stephen?
> 
> Yes, I'll be breaking them up and sending them to you in a few days so
> Stephen doesn't have to handle all of this.  Right now it's in a single
> patch file that touches about 400+ files :)

Of course, it is even better when I don't have to track them at all :-)

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-05-30  0:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-29  2:18 linux-next: pci/driver-core merge conflicts Stephen Rothwell
2008-05-29  2:59 ` Greg KH
2008-05-29 15:57   ` Jesse Barnes
2008-05-29 16:02     ` Greg KH
2008-05-30  0:55       ` Stephen Rothwell [this message]
2008-05-30  0:53     ` 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=20080530105509.34faa639.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=greg@kroah.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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).