public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Collins <ben.collins@ubuntu.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH updated]: How to be a kernel driver maintainer
Date: Mon, 09 Jan 2006 19:58:51 -0500	[thread overview]
Message-ID: <1136854731.4620.4.camel@grayson> (raw)
In-Reply-To: <1136842100.2936.34.camel@laptopd505.fenrus.org>

So is there a document I can point to that explains how to maintain your
code properly? It's somewhat out of scope, so I really don't want a
HOWTO within a HOWTO.

-- 
   Ben Collins <ben.collins@ubuntu.com>
   Developer
   Ubuntu Linux


  parent reply	other threads:[~2006-01-10  0:59 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-08 16:07 [PATCH]: How to be a kernel driver maintainer Ben Collins
2006-01-08 16:33 ` Arjan van de Ven
2006-01-08 18:27   ` Ben Collins
2006-01-08 18:43     ` Arjan van de Ven
2006-01-08 18:57       ` Arjan van de Ven
2006-01-09  9:51       ` Joel Becker
2006-01-08 21:45 ` [PATCH updated]: " Ben Collins
2006-01-09  7:46   ` Arjan van de Ven
2006-01-09 13:34     ` Ben Collins
2006-01-09 14:02       ` Grant Coady
2006-01-09 21:28       ` Arjan van de Ven
2006-01-10  0:09         ` Linus Torvalds
2006-01-10  0:58         ` Ben Collins [this message]
2006-03-08 18:03         ` [Updated]: How to become " Ben Collins
2006-03-08 19:05           ` Jesper Juhl
2006-03-08 19:10             ` Arjan van de Ven
2006-03-08 19:27               ` Jesper Juhl
2006-06-02 21:38                 ` [Updated v3]: " Ben Collins
2006-06-02 22:16                   ` Randy.Dunlap
2006-06-03  0:03                   ` Greg KH
2006-06-05 10:27                   ` Jan Engelhardt
2006-03-09  4:32           ` [Updated]: " Randy.Dunlap
2006-01-08 21:47 ` [PATCH]: How to be " Ben Collins
2006-01-09 19:26 ` Pavel Machek
2006-01-10 15:10   ` Ben Collins

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=1136854731.4620.4.camel@grayson \
    --to=ben.collins@ubuntu.com \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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