From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH][meta-oe] lmbench: Added 3.0-a9 version recipe files
Date: Tue, 23 Aug 2011 17:15:16 +0200 [thread overview]
Message-ID: <j30g64$n1v$1@dough.gmane.org> (raw)
In-Reply-To: <1314112164.3688.17.camel@mattotaupa>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 23-08-11 17:09, Paul Menzel schreef:
> Am Montag, den 22.08.2011, 19:13 +0200 schrieb Paul Menzel:
>
>> Am Montag, den 22.08.2011, 19:32 +0500 schrieb Noor, Ahsan:
>
>>> +SRC_URI = "${SOURCEFORGE_MIRROR}/lmbench/lmbench-${PV}.tgz \ + file://lmbench-run \ + file://rename-line-binary.patch \ + file://update-results-script.patch \ + file://obey-ranlib.patch"
>>
>> Please add `\` at the end and put " on the new line.
>
> As to your question on IRC why this is useful. My reasoning is, that in the future patch diffs will be smaller when adding a new line to the end of `SRC_URI`. But in the end it is just taste and no hard rule.
It also makes it easier to copy/paste a line into the end of the SRC_URI instead of making it the second to last entry :)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFOU8QEMkyGM64RGpERAmB+AJ90xGGui+WJPBA7Yr/PI5MeurfYpACcCtAu
YzAmqSIWY11e1G1PrDHnQ28=
=2SnN
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2011-08-23 15:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-22 14:32 [PATCH][meta-oe] lmbench: Added 3.0-a9 version recipe files Noor, Ahsan
2011-08-22 15:39 ` Ahsan, Noor
2011-08-22 17:13 ` Tom Rini
2011-08-22 17:13 ` Paul Menzel
2011-08-22 17:17 ` Tom Rini
2011-08-22 18:18 ` Paul Menzel
2011-08-23 15:09 ` Paul Menzel
2011-08-23 15:15 ` Koen Kooi [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='j30g64$n1v$1@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--cc=openembedded-devel@lists.openembedded.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