Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.nop@aon.at>
To: buildroot@busybox.net
Subject: [Buildroot] [patch] qtopia4
Date: Tue, 12 Dec 2006 11:21:09 +0100	[thread overview]
Message-ID: <20061212102109.GA5767@aon.at> (raw)
In-Reply-To: <37c712e0612120205p5c580f20k7696bbfe24626093@mail.gmail.com>

On Tue, Dec 12, 2006 at 06:05:31PM +0800, Allan Clark wrote:
>On 12/12/06, Thomas Lundquist <lists@zelow.no> wrote:
>> On Mon, Dec 11, 2006 at 11:27:08PM +0100, Bernhard Fischer wrote:
>> [...]
>>
>> > >It's a habit. Any real reason we should make it a requirement not to
>> > >have it or is it just for looks?
>> >
>> > Well, it's bloat :) Habit of mine to omit them if they are not needed.
>>
>> hehe.
>>
>> but space isn't much of an issue in the buildroot scripts.
>
>(I think we're still tlaking about ";")

We do indeed.
>
>I'm involved in a project where a ";" instead of a "&&" between two
>dependent build steps is evil, naughty, and generally bad.  Seems the

Note that we're talking about the command-separator of sed.

I don't buy the argument that "space isn't much of an issue in the
buildroot scripts", fwiw.

Just don't add bloat in the first place, especially when it's
superfluous, doesn't serve any purpose whatsoever etc. Anywhere.
Anytime. At any rate.

It's a no-go.
Grossly OT, though. :P

  reply	other threads:[~2006-12-12 10:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-11  9:33 [Buildroot] [patch] qtopia4 Thomas Lundquist
2006-12-11 10:24 ` Bernhard Fischer
2006-12-11 10:48   ` Ulf Samuelsson
2006-12-11 12:00   ` Thomas Lundquist
2006-12-11 13:43     ` Bernhard Fischer
2006-12-11 21:56       ` Thomas Lundquist
2006-12-11 22:27         ` Bernhard Fischer
2006-12-12  8:38           ` Thomas Lundquist
2006-12-12 10:05             ` Allan Clark
2006-12-12 10:21               ` Bernhard Fischer [this message]
2006-12-12 15:43               ` Thomas Lundquist
2006-12-13 20:09             ` Bernhard Fischer

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=20061212102109.GA5767@aon.at \
    --to=rep.nop@aon.at \
    --cc=buildroot@busybox.net \
    /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