From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v7] wine: New package
Date: Sun, 22 Feb 2015 22:11:17 +0100 [thread overview]
Message-ID: <20150222211117.GH4016@free.fr> (raw)
In-Reply-To: <54EA42C0.9010608@dawncrow.de>
Andre, All,
On 2015-02-22 21:57 +0100, Andr? Hentschel spake thusly:
> >> +ifeq ($(BR2_TOOLCHAIN_EXTERNAL),y)
> >> + WINE_CONF_OPTS += TARGETFLAGS="-b $(call qstrip,$(BR2_TOOLCHAIN_EXTERNAL_PREFIX))"
> >
> > We usually do not indent the variable assignements in conditional
> > blocks.
>
> I've seen it that way (same goes for the dependencies checking) and i think it's much nicer that way...
> Is this minor enough to keep it that way?
Well, I'd prefer we don't indent, since we don't do that anywhere else
(well, there are a very few packages that do, but they are old, very
old; the rule is not to indent).
> > I'm doing a few test builds, and will respin an amended version of this
> > patch.
>
> no need for a respin, your comments will simply end up in v8
OK, great!
Just respin it tonight if you don't have more comments shortly.
I know Thomas wanted to look at it and apply it soonish. :-)
Thanks!
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. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2015-02-22 21:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 19:20 [Buildroot] [PATCH v7] wine: New package André Hentschel
2015-02-22 20:42 ` Yann E. MORIN
2015-02-22 20:57 ` André Hentschel
2015-02-22 21:11 ` Yann E. MORIN [this message]
2015-02-22 21:26 ` Yann E. MORIN
2015-02-23 19:18 ` André Hentschel
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=20150222211117.GH4016@free.fr \
--to=yann.morin.1998@free.fr \
--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