From: justin <jlec@gentoo.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] menuconfig: use config scripts to detect ncurses libs
Date: Thu, 28 Feb 2013 22:35:59 +0100 [thread overview]
Message-ID: <512FCDBF.5050508@gentoo.org> (raw)
In-Reply-To: <201302281916.00257.yann.morin.1998@free.fr>
[-- Attachment #1: Type: text/plain, Size: 431 bytes --]
On 2/28/13 7:16 PM, Yann E. MORIN wrote:
> And, sorry, I should have been more explicit in my previous mail that
> the legacy drop should be in its own patch. I thought that was obvious,
> following the "one single change per patch" philosophy.
>
Hi,
no worries. I will submit as you suggested. It's a learning experience
for me and we will get this solved.
The new patches will come tomorrow.
Thanks,
Justin
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 268 bytes --]
next prev parent reply other threads:[~2013-02-28 21:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 11:52 [PATCH] menuconfig: use config scripts to detect ncurses libs jlec
2013-02-28 18:16 ` Yann E. MORIN
2013-02-28 21:35 ` justin [this message]
2013-03-01 11:50 ` Michal Marek
2013-03-03 20:13 ` Yann E. MORIN
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=512FCDBF.5050508@gentoo.org \
--to=jlec@gentoo.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yann.morin.1998@free.fr \
/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