From: Michal Marek <mmarek@suse.cz>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org, Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [pull request] Pull request for branch yem-kconfig-for-next
Date: Thu, 02 May 2013 10:48:36 +0200 [thread overview]
Message-ID: <51822864.4060304@suse.cz> (raw)
In-Reply-To: <cover.1367258255.git.yann.morin.1998@free.fr>
On 29.4.2013 19:59, Yann E. MORIN wrote:
> The following changes since commit 23a5dfdad22a574d19d7cc19b391f9ce0d3c2f21:
>
> Revert "kconfig: fix randomising choice entries in presence of KCONFIG_ALLCONFIG" (2013-04-26 23:21:59 +0200)
>
> are available in the git repository at:
>
> git://gitorious.org/linux-kconfig/linux-kconfig.git yem-kconfig-for-next
Pulled, thanks.
Michal
next prev parent reply other threads:[~2013-05-02 8:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 17:59 [pull request] Pull request for branch yem-kconfig-for-next Yann E. MORIN
2013-04-29 17:59 ` [PATCH 1/1] kconfig: fix lists definition for C++ Yann E. MORIN
2013-04-29 19:28 ` Randy Dunlap
2013-04-29 21:54 ` Rob Landley
2013-04-29 22:30 ` Yann E. MORIN
2013-04-29 22:57 ` Rob Landley
2013-05-02 8:48 ` Michal Marek [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-06-29 14:21 [pull request] Pull request for branch yem-kconfig-for-next Yann E. MORIN
2013-06-18 22:44 Yann E. MORIN
2013-06-19 20:40 ` Michal Marek
2013-06-19 21:01 ` Yann E. MORIN
2013-04-26 22:17 Yann E. MORIN
2013-04-29 12:09 ` Michal Marek
2013-04-22 21:31 Yann E. MORIN
2013-04-23 7:07 ` Yann E. MORIN
2013-02-09 0:58 Yann E. MORIN
2013-02-16 11:18 ` Yann E. MORIN
2013-02-19 12:43 ` Michal Marek
2013-02-19 18:16 ` Yann E. MORIN
2013-02-20 9:57 ` Michal Marek
2013-01-15 23:12 Yann E. MORIN
2013-01-24 10:44 ` Michal Marek
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=51822864.4060304@suse.cz \
--to=mmarek@suse.cz \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.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