From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Dirk Gouders <dirk@gouders.net>,
Jan Beulich <JBeulich@novell.com>, Michal Marek <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org
Subject: Re: kconfig/menu.c: Fixup to "kconfig: fix undesirable side effect of adding "visible" menu attribute" ?
Date: Fri, 2 Aug 2013 18:48:27 +0200 [thread overview]
Message-ID: <20130802164827.GA3349@free.fr> (raw)
In-Reply-To: <CA+icZUVzFVoEQWO-xAV-Ktc45CSV5rucwMsOu3D1Vq3jtTAibw@mail.gmail.com>
On 2013-08-02 18:10 +0200, Sedat Dilek spake thusly:
> On Fri, Aug 2, 2013 at 10:59 AM, Dirk Gouders <dirk@gouders.net> wrote:
> > One non-technical remark: I am quite unconfortable with the way I got
> > drawn into the "discussion" on freetz.org -- especially, because I
> > prefer to maintain a respectful discussion style that is focussed on
> > technical problems. (Probably, I sometimes appear to break my own rule
> > but hopefully others notice that English isn't my mother tongue and am
> > just incorrectly using a foreign language.)
> >
> > My feeling is that besides a technical problem with a patch there is
> > an unresolved conflict that I have nothing to do with and don't want to
> > be drawn into.
Agreed. If the Freetx community is not willing to explain their issue
with a meaningful explanation, there is no reason we continue this
thread here.
I have to side with Dirk on this. I am willing to help solve kconfig
issues as a global betterment of the situation (he! problems in
third-party projects may well be applicable to the kernel too).
> Short: Best do the discussion here, not in the Freetz BTS.
No, we can not discuss it here anymore (IMHO) since the Freetz community
is not willing to help. It's now their problem, until they come up with
a complete and clear explanation, that has to be way better than "it is
broken".
So, I suggest we close this thread for now. At least, I will not
participate further into this.
Thank you! :-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2013-08-02 16:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 17:11 kconfig/menu.c: Fixup to "kconfig: fix undesirable side effect of adding "visible" menu attribute" ? Sedat Dilek
2013-07-31 14:16 ` Dirk Gouders
2013-07-31 14:22 ` Sedat Dilek
2013-07-31 16:53 ` Yann E. MORIN
2013-07-31 17:12 ` Sedat Dilek
2013-08-01 6:21 ` Dirk Gouders
2013-08-01 6:51 ` Sedat Dilek
2013-08-01 7:01 ` Sedat Dilek
2013-08-01 7:17 ` Sedat Dilek
2013-08-02 6:11 ` Sedat Dilek
2013-08-02 8:59 ` Dirk Gouders
2013-08-02 16:10 ` Sedat Dilek
2013-08-02 16:48 ` Yann E. MORIN [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=20130802164827.GA3349@free.fr \
--to=yann.morin.1998@free.fr \
--cc=JBeulich@novell.com \
--cc=dirk@gouders.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sedat.dilek@gmail.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