From: Mikhail Gusarov <dottedmag@dottedmag.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Default SRCREV value
Date: Thu, 20 Mar 2008 14:06:40 +0600 [thread overview]
Message-ID: <87tzj1lsz3.fsf@frontier.dottedmag.net> (raw)
In-Reply-To: <200803200120.47119.zecke@selfish.org> (Holger Freyther's message of "Thu, 20 Mar 2008 01:20:47 +0100")
[-- Attachment #1: Type: text/plain, Size: 519 bytes --]
Twas brillig at 01:20:47 20.03.2008 UTC+01 when Holger Freyther did gyre and gimble:
HF> The only down-side I can think of, now parsing will fail for a
HF> recipe you do not even care for in your distribution, with having a
HF> default value 1 you just parse fine.
Is it possible to handle recipies a bit lazier, to avoid recipies which
are not interesting?
Hmm... In other hand, until recipie is not parsed, it is not possible to
say whether it is needed for build or not, so it can be tricky.
--
[-- Attachment #2: Type: application/pgp-signature, Size: 196 bytes --]
next prev parent reply other threads:[~2008-03-20 8:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 23:31 Default SRCREV value Mikhail Gusarov
2008-03-19 23:50 ` Philip Balister
2008-03-20 0:20 ` Holger Freyther
2008-03-20 2:04 ` Philip Balister
2008-03-20 8:06 ` Mikhail Gusarov [this message]
2008-03-20 9:46 ` Leon Woestenberg
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=87tzj1lsz3.fsf@frontier.dottedmag.net \
--to=dottedmag@dottedmag.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