From: "Bernhard Seßler" <bernhard.sessler@corscience.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] tntnet: Add host package
Date: Mon, 17 Feb 2014 07:57:44 +0100 [thread overview]
Message-ID: <5301B2E8.4070109@corscience.de> (raw)
In-Reply-To: <20140211113200.GC29011@pengutronix.de>
Hi folks,
sorry, I've been on vacation last week and I was not thinking about IT related
stuff even once. ;)
On 11.02.2014 12:32, Michael Olbrich wrote:
> On Tue, Feb 11, 2014 at 12:23:21PM +0100, Juergen Beisert wrote:
>> On Tuesday 11 February 2014 12:02:33 Michael Olbrich wrote:
>> > [...]
>> > > +
>> > > +config HOST_TNTNET
>> > > + tristate
>> > > + default ALLYES
>> > > + select HOST_ZLIB
>> > > + help
>> > > + web application server for c++
>> >
>> > You can drop the help here. It's not visible anyways.
>>
>> Some people tend to add comments into their C-code which is also not visible
>> after the compiler has done its job. But for the readers of the C-code these
>> comments are still helpful.
>
> The target package has the same comment, so it's just duplicated. And it's
> not exactly correct. The host package is just for code generation.
>
> Michael
>
I tend to agree to Michael, I will drop the help text (as already stated it's
not visible anywhere and one might also look up the help text in the target
package). And I will add a dependency to a host cxxtools package (don't know why
I've not seen this myself).
Thanks for the hints.
Regards,
Bernhard
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-02-17 6:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 12:42 Bernhard Sessler
2014-02-11 11:02 ` Michael Olbrich
2014-02-11 11:23 ` Juergen Beisert
2014-02-11 11:32 ` Michael Olbrich
2014-02-17 6:57 ` Bernhard Seßler [this message]
2014-02-18 7:13 ` Bernhard Seßler
2014-02-12 8:55 ` Michael Olbrich
2014-02-12 8:57 ` Michael Olbrich
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=5301B2E8.4070109@corscience.de \
--to=bernhard.sessler@corscience.de \
--cc=ptxdist@pengutronix.de \
/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