From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] lcdproc: remove patch rejected upstream
Date: Fri, 16 Nov 2012 00:07:21 +0100 [thread overview]
Message-ID: <878va21n4m.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1352720842-5781-1-git-send-email-spdawson@gmail.com> (spdawson@gmail.com's message of "Mon, 12 Nov 2012 11:47:21 +0000")
>>>>> "spdawson" == spdawson <spdawson@gmail.com> writes:
spdawson> From: Simon Dawson <spdawson@gmail.com>
spdawson> Remove an lcdproc patch which has been rejected upstream. It has been
spdawson> decided by lcdproc developer Markus Dolze that the behaviour of the
spdawson> client_add_key command when handling the minus key is "intentional to
spdawson> some degree."
spdawson> This patch also takes the opportunity to remove the version
spdawson> number from the single remaining lcdproc patch.
Committed, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2012-11-15 23:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 11:47 [Buildroot] [PATCH] lcdproc: remove patch rejected upstream spdawson at gmail.com
2012-11-15 23:07 ` Peter Korsgaard [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=878va21n4m.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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