From: Jens Axboe <axboe@suse.de>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [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
Date: Sun, 20 Oct 2002 12:13:43 +0200 [thread overview]
Message-ID: <20021020101343.GO871@suse.de> (raw)
In-Reply-To: <1035108575.3130.10.camel@localhost.localdomain>
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
next prev parent reply other threads:[~2002-10-20 10:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-20 9:35 [PATCH] ext2/3 updates for 2.5.44 (1/11): Default mount options in superblock tytso
2002-10-20 10:09 ` [LARGE patch 23/124] sets sent over and over again " Arjan van de Ven
2002-10-20 10:13 ` Jens Axboe [this message]
2002-10-20 10:31 ` Russell King
2002-10-20 10:35 ` Arjan van de Ven
2002-10-20 11:07 ` longjmp/setjmp in kernel Keith Owens
2002-10-20 12:39 ` [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 Nicholas Wourms
2002-10-20 16:44 ` Richard Gooch
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=20021020101343.GO871@suse.de \
--to=axboe@suse.de \
--cc=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.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