From: Oleg Verych <olecom@flower.upol.cz>
To: Richard Knutsson <ricknu-0@student.ltu.se>
Cc: Andrew Morton <akpm@osdl.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [SCRIPT] Remove "space damage" from patches
Date: Mon, 29 Jan 2007 02:27:42 +0000 [thread overview]
Message-ID: <20070129022742.GA26765@flower.upol.cz> (raw)
In-Reply-To: <45BD5543.5020704@student.ltu.se>
On Mon, Jan 29, 2007 at 03:00:35AM +0100, Richard Knutsson wrote:
> Oleg Verych wrote:
> >On Mon, Jan 29, 2007 at 02:26:04AM +0100, Richard Knutsson wrote:
> >[]
> >
> >>I also guess you saw that the script is _not_ for cleaning up
> >>source-files (can be intrusive and is better to be fixed when fixing
> >>something else), but patches.
> >>
> >
> >IMHO it's dealing with consequences, not cause, and it's even worse.
> >
> How many patches is not to fix bugs, it is worse then some strayed
> whitespace but it is due to reality.
> The best is, of course, if neither happened but the next best thing is
1. Patches are signed-off (not by you).
2. Maybe Andrew Morton under his sign-off add such feature.
> >> (otherwise I believe they just deleted my mail ;) ).
> >>
> >
> >I would like to discuss, would you?
> >
> I like to discuss but I am not sure what the result would be. Force
> people to use the editors of our choice?
> As long people uses valid e-mail-clients when sending patches (or they
> use the script "sendpatchset"), I'm think we have to be satisfied.
> But if you have any ideas, I'm listening.
Open-source worker, hammering his fingers? Please, let me out it ;D
> Richard Knutsson
>
_____
prev parent reply other threads:[~2007-01-29 2:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-28 21:37 [SCRIPT] Remove "space damage" from patches Richard Knutsson
2007-01-28 22:52 ` Oleg Verych
2007-01-29 0:08 ` Richard Knutsson
2007-01-29 0:31 ` Oleg Verych
2007-01-29 1:26 ` Richard Knutsson
2007-01-29 1:43 ` Oleg Verych
2007-01-29 2:00 ` Richard Knutsson
2007-01-29 2:27 ` Oleg Verych [this message]
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=20070129022742.GA26765@flower.upol.cz \
--to=olecom@flower.upol.cz \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ricknu-0@student.ltu.se \
/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