From: Tim Bird <tim.bird@am.sony.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
linux-embedded <linux-embedded@vger.kernel.org>,
linux kernel <linux-kernel@vger.kernel.org>,
David Woodhouse <dwmw2@infradead.org>,
Holger Schurig <hs4233@mail.mn-solutions.de>
Subject: Re: [PATCH] add diffconfig utility
Date: Thu, 12 Jun 2008 09:07:24 -0700 [thread overview]
Message-ID: <485149BC.4070901@am.sony.com> (raw)
In-Reply-To: <20080612131931.GB13702@uranus.ravnborg.org>
Sam Ravnborg wrote:
> Hi Tim.
>
>> The program is also now better structured, IMHO.
>> -- Tim
>
> Seeing this programs gets frequent updates (good!) I have not
> yet applied it.
>
> When you consider it stabilized could you please drop me a
> new mail including full changelog and updated patch.
>
> And please cc: linux-kbuild@vger.kernel.org + linux-kernel on the
> submission.
Will do. I'll give it a little settle time, and then
notify you.
-- Tim
=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Corporation of America
=============================
next prev parent reply other threads:[~2008-06-12 16:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 19:41 Tim Bird
2008-06-10 21:02 ` Jörn Engel
2008-06-10 21:18 ` Sam Ravnborg
2008-06-10 21:33 ` execute bit on scripts (was Re: [PATCH] add diffconfig utility) Tim Bird
2008-06-10 22:26 ` Jan Engelhardt
2008-06-10 21:21 ` [PATCH] add diffconfig utility Sam Ravnborg
2008-06-11 0:25 ` Tim Bird
2008-06-11 11:28 ` Geert Uytterhoeven
2008-06-11 18:23 ` Tim Bird
2008-06-12 13:19 ` Sam Ravnborg
2008-06-12 16:07 ` Tim Bird [this message]
2008-06-24 17:56 ` [PATCH] add diffconfig utility (v2) Tim Bird
2008-06-25 5:36 ` Greg KH
2008-06-27 21:10 ` Sam Ravnborg
2008-06-10 22:07 ` [PATCH] add diffconfig utility David Woodhouse
2008-06-10 22:33 ` Tim Bird
2008-06-10 23:02 ` Arjan van de Ven
2008-06-10 23:10 ` David Woodhouse
2008-06-11 6:59 ` Holger Schurig
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=485149BC.4070901@am.sony.com \
--to=tim.bird@am.sony.com \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=dwmw2@infradead.org \
--cc=hs4233@mail.mn-solutions.de \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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
Powered by JetHome