All of lore.kernel.org
 help / color / mirror / Atom feed
From: Domen Puncer <domen@coderock.org>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Krzysztof Halasa <khc@pm.waw.pl>,
	kernel-mentors@selenic.com, haveblue@us.ibm.com,
	Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] update SubmittingPatches to clarify attachment policy
Date: Sun, 15 May 2005 00:10:19 +0200	[thread overview]
Message-ID: <20050514221019.GA22145@nd47.coderock.org> (raw)
In-Reply-To: <20050504122836.69205a04.rddunlap@osdl.org>

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

On 04/05/05 12:28 -0700, Randy.Dunlap wrote:
> A couple of days ago, Matt Mackall described/proposed a tool to
> check new patches for acceptable content and format:
>   http://www.selenic.com/pipermail/kernel-mentors/2005-May/000072.html
> 
> I'm attaching a rudimentary version of such a tool (check-patch.pl).
> It does not attempt to check for line wrapping or lines that are
> > 80 characters.

I made a simpler (it's only regexes :-) ) and uglier version, which
does check for line wrapping.
I probably won't have too much time to work on it, so feel free
to do whatever you want with it.

> It dislikes patches that contain attachments that are base64,
> quoted-printable, or binary (e.g.).
> 
> People can run this script locally, but ideally We (royal) will
> have an email address for it so that people can use it to check
> if their mail interface munges the patch for them... :(
> and can try again until it doesn't.

I put mine on patch-tester@coderock.org ... don't abuse it too
much, it's just an old pentium on adsl there :-)


	Domen

[-- Attachment #2: patch-tester.pl --]
[-- Type: application/x-perl, Size: 2922 bytes --]

  reply	other threads:[~2005-05-14 22:10 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-04 17:01 [RFC][PATCH] update SubmittingPatches to clarify attachment policy Dave Hansen
2005-05-04 17:10 ` Jon Smirl
2005-05-04 17:54   ` Jan-Benedict Glaw
2005-05-04 18:23     ` Richard B. Johnson
2005-05-05  8:12       ` Jan-Benedict Glaw
2005-05-05 16:43         ` Lee Revell
2005-05-05 17:31           ` Jan-Benedict Glaw
2005-05-04 20:42   ` Rafael J. Wysocki
2005-05-04 17:15 ` Dmitry Torokhov
2005-05-04 17:16 ` Valdis.Kletnieks
2005-05-04 17:25   ` Dave Hansen
2005-05-04 17:55     ` Chris Wright
2005-05-04 18:14       ` Dave Hansen
2005-05-04 19:21         ` Alexander Nyberg
2005-05-05 19:06         ` Jeff Garzik
2005-05-04 17:58     ` Dipankar Sarma
2005-05-04 18:52     ` Krzysztof Halasa
2005-05-04 19:28       ` Randy.Dunlap
2005-05-14 22:10         ` Domen Puncer [this message]
2005-05-04 17:59 ` John W. Linville
2005-05-05  1:09 ` Rik van Riel
2005-05-05  9:07   ` Geert Uytterhoeven
2005-05-05 10:06   ` Krzysztof Halasa
2005-05-05 12:01     ` Paulo Marques
2005-05-05 21:34       ` Steven Cole
2005-05-06  1:31         ` Lee Revell
2005-05-06  4:05           ` Valdis.Kletnieks
     [not found] <40vxU-1a1-25@gated-at.bofh.it>
     [not found] ` <40vRd-1os-1@gated-at.bofh.it>
2005-05-05  2:36   ` Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org>

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=20050514221019.GA22145@nd47.coderock.org \
    --to=domen@coderock.org \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=haveblue@us.ibm.com \
    --cc=kernel-mentors@selenic.com \
    --cc=khc@pm.waw.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@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 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.