From: Pavel Roskin <proski@gnu.org>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: linux-wireless@vger.kernel.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] compat-wireless: add linux-next-pending, crap patch dirs and nagometer
Date: Fri, 21 May 2010 21:15:36 -0400 [thread overview]
Message-ID: <1274490936.3439.14.camel@ct> (raw)
In-Reply-To: <1274489059-1019-1-git-send-email-lrodriguez@atheros.com>
On Fri, 2010-05-21 at 20:44 -0400, Luis R. Rodriguez wrote:
> Sometimes you have no other option but to carry around patches.
> This can happen for a variety of reasons. Ultimately testing of code
> cannot happen on the kernel maintainer's clock but on your own.
>
> This expands the idea of the linux-next-cherry-pick patch directory
> on compat-wireless to also allow for patches to be merged which are
> posted to some mailing list but pending merge due to some reasons
> (merge window is a good example). It also adds a crap patch directory
> for those really nasty situations you can run into where you have
> no other option but to give someone a release with some delta even
> if the patch is not yet posted anywhere.
Please replace "crap" with some more descriptive name, like
"unpublished". It's better to be friendly to users and express
frustration in a different way.
> + printf "${RED}%10s${NORMAL} - Crap changes not yet posted\n" $2
> + printf "${RED}%10s${NORMAL} - Crap additions not yet merged\n" $3
> + printf "${RED}%10s${NORMAL} - Crap deletions not yet posted\n" $4
You want "not yet posted" in all cases.
"Crap deletions" may be offensive for Linux contributors whose code is
being deleted. Besides, if patches are not posted, somebody still spent
time on making them. Let's not discourage those who care.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2010-05-22 1:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-22 0:44 [PATCH] compat-wireless: add linux-next-pending, crap patch dirs and nagometer Luis R. Rodriguez
2010-05-22 1:15 ` Pavel Roskin [this message]
2010-05-22 1:19 ` Luis R. Rodriguez
2010-05-22 1:28 ` Luis R. Rodriguez
2010-05-22 1:42 ` Luis R. Rodriguez
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=1274490936.3439.14.camel@ct \
--to=proski@gnu.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
/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