linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Michael Hunold <hunold@convergence.de>
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [PATCH[[2.5][3-11] update dvb subsystem core
Date: Wed, 7 May 2003 16:59:36 +0100	[thread overview]
Message-ID: <20030507165935.A29161@infradead.org> (raw)
In-Reply-To: <3EB92CAD.2040502@convergence.de>; from hunold@convergence.de on Wed, May 07, 2003 at 05:56:29PM +0200

On Wed, May 07, 2003 at 05:56:29PM +0200, Michael Hunold wrote:
> I promise that I don't touch the devfs related code anymore.

Oh, you can of course touch it again in future, I just want to
finish the API transition first, I hope I'll be done by the end of this
week.

> But, how do 
> we proceed in general?
> 
> Will the other patches be applied and who does that for which tree?
> Shall I resend the patches where you had objections?

As nothing got in yet I'd suggest resending everything, with Linus you
sometimes may have to resend quite often anyway :)

  reply	other threads:[~2003-05-07 15:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-06 16:04 [PATCH[[2.5][3-11] update dvb subsystem core Michael Hunold
2003-05-06 20:49 ` Christoph Hellwig
2003-05-07  9:19   ` Michael Hunold
2003-05-07  9:28     ` Christoph Hellwig
2003-05-07 15:56       ` Michael Hunold
2003-05-07 16:04         ` Christoph Hellwig
2003-05-06 21:08 ` Christoph Hellwig
2003-05-07  8:40   ` Michael Hunold
2003-05-07  9:22     ` Christoph Hellwig
2003-05-07 15:56       ` Michael Hunold
2003-05-07 15:59         ` Christoph Hellwig [this message]
2003-05-07 16:14           ` Michael Hunold
2003-05-07 16:15             ` Christoph Hellwig
2003-05-07 18:30             ` Alan Cox

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=20030507165935.A29161@infradead.org \
    --to=hch@infradead.org \
    --cc=hunold@convergence.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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).