public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Timothy Miller <miller@techsource.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: vonbrand@inf.utfsm.cl, jgarzik@pobox.com, dwmw2@infradead.org,
	linux-kernel@vger.kernel.org, akpm@osdl.org, jeremy@sgi.com
Subject: Re: [DOC] Linux kernel patch submission format
Date: Wed, 20 Oct 2004 15:34:50 -0400	[thread overview]
Message-ID: <4176BDDA.1020406@techsource.com> (raw)
In-Reply-To: <20040924082241.6bb1c849.rddunlap@osdl.org>



Randy.Dunlap wrote:
> On Fri, 24 Sep 2004 11:04:38 -0400 Timothy Miller wrote:
> 
> | 
> | 
> | Horst von Brand wrote:
> | > Timothy Miller <miller@techsource.com> said:
> | > 
> | >>Does the Linux kernel source tree include a shell script which will 
> | >>compare two trees, create patches, and ask the necessary questions so as 
> | >>to format the files correctly with all the right stuff?
> | > 
> | > 
> | > diff(1) does what you want...
> | 
> | So, in addition to producing the difference, diff also asks you all the 
> | questions necessary for a Linux kernel submission, properly formats 
> | them, and adds them to the diff output?
> 
> Of course not.  There is no script in the kernel tree that does
> what you asked... but you probably knew that.
> 
> Is one really needed?  or maybe a GUI IDE is all that is required.

Yes, it's needed.

Rather than having a strict policy which many people are going to 
violate because they don't understand all the intricacies, it would be 
beneficial to have a script that everyone uses which enforces all the rules.

Among other things, this reduces confusion and the barrier to entry.

More patches will be acceptable, and no one will ever have to clean up a 
patch which is really important but just not formatted quite right.

Hey, think about it.  We're computer geeks who should understand very 
well how computers can be used as tools to automate processes, taking 
the burden off of humans.  Given that dozens of patches are posted every 
day, this seems like a prime candidate for automation!

Furthermore, the script can be written to do interesting and helpful 
things that no one would consider putting into the policy because they 
would be too bothersome for the user to do.

If I knew bash, perl, python, or any other scripting language, I would 
volunteer.  I don't think you'd like my horribly non-portable C or C++ 
version, and I don't think Verilog, PHP, or Javascript would quite do 
the job either.  :)


  reply	other threads:[~2004-10-21  6:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-31  8:08 [DOC] Linux kernel patch submission format Jeff Garzik
2004-08-31 11:41 ` Neil Horman
2004-08-31 16:17 ` Erik Mouw
2004-08-31 16:37 ` David Woodhouse
2004-08-31 17:15   ` Jeff Garzik
2004-08-31 17:17     ` David Woodhouse
2004-08-31 17:25       ` Jeff Garzik
2004-09-01  1:27       ` Lee Revell
2004-09-22 18:59     ` Timothy Miller
2004-09-22 19:47       ` Horst von Brand
2004-09-23  7:46         ` Paul Jackson
2004-09-24 15:04         ` Timothy Miller
2004-09-24 15:22           ` Randy.Dunlap
2004-10-20 19:34             ` Timothy Miller [this message]
2004-08-31 17:07 ` Sam Ravnborg
2004-08-31 17:11   ` Jeff Garzik
2004-08-31 17:50 ` Patrick Dreker
2004-08-31 18:01   ` Jeff Garzik

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=4176BDDA.1020406@techsource.com \
    --to=miller@techsource.com \
    --cc=akpm@osdl.org \
    --cc=dwmw2@infradead.org \
    --cc=jeremy@sgi.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.org \
    --cc=vonbrand@inf.utfsm.cl \
    /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