lkml.org 
[lkml]   [2002]   [Oct]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [LARGE patch 23/124] sets sent over and over again Re: [PATCH] ext2/3 updates for 2.5.44 (1/11): Default mount options in superblock
On Sun, Oct 20 2002, Arjan van de Ven wrote:
> Hi,
>
> I know everybody wants to be cool and split their patchkit up. I'm all
> for that. But why oh why do these sets have to be sent to LKML every
> time when a new upstream kernel is released and the only change is a
> rsync? (and Ted, this is not meant as a personal assault of any kind,
> your mail was just the one that was the final drop in the bucket)
>
> I hereby politely ask EVERYONE who wants to (re)posts large patchsets,
> to at minimum try to follow something like the following politeness
> guidelines
>
> 1) Make it ONE thread. Do this by cc or bcc'ing yourself on the mails
> and use the reply feature of your mailer to reply each next number of
> the set to the previous one. This allows people that use mail/news
> readers that can do threading to properly sort it. This is not hard,
> and I consider it the least you can do for the people that read lklm.
>
> 2) Do not resent all 506 parts of your patchkit every time Linus
> releases a new kernel and all you did was merge up. Post 1 mail with
> the fact that you did this and an URL to the patchkit if you feel
> everyone and their dog really wants to know this fact. This does not
> mean that if you did significant cleanup work you shouldn't repost
> (while keeping #1 in mind), that obviously is of more interest.

Well said, I couldn't agree more.

--
Jens Axboe

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:30    [W:0.053 / U:0.308 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site