From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] flex: updated to 2.5.37
Date: Fri, 10 May 2013 11:32:12 +0100 [thread overview]
Message-ID: <1368181932.11129.11.camel@ted> (raw)
In-Reply-To: <20130510102041.GA12329@jama.dyndns-home.com>
On Fri, 2013-05-10 at 12:20 +0200, Martin Jansa wrote:
> On Fri, May 10, 2013 at 01:15:10PM +0300, Bogdan Marinescu wrote:
> > Removed the patches to flex, because they are now applied to the
> > latest version.
>
> Can you check if 2.5.37 still reports flex.real when you call
> flex --version?
>
> If yes, please integrate
> http://lists.linuxtogo.org/pipermail/openembedded-core/2013-May/039425.html
> I'll send v2 with added ${S} in a minute
I'm really not convinced we should be hacking flex to fix this. Can't
whatever parsing is being done to extract the version be a little more
relaxed about the name?
Cheers,
Richard
next prev parent reply other threads:[~2013-05-10 10:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 10:15 [PATCH] flex: updated to 2.5.37 Bogdan Marinescu
2013-05-10 10:13 ` Marinescu, Bogdan A
2013-05-10 10:20 ` Martin Jansa
2013-05-10 10:32 ` Richard Purdie [this message]
2013-05-10 10:37 ` Martin Jansa
2013-05-10 10:46 ` Phil Blundell
2013-05-10 10:50 ` Phil Blundell
2013-05-10 11:00 ` Burton, Ross
2013-05-12 7:32 ` Richard Purdie
2013-05-27 7:48 ` Marinescu, Bogdan A
-- strict thread matches above, loose matches on Subject: below --
2013-01-31 11:53 Bogdan Marinescu
2013-01-31 16:30 ` Richard Purdie
2013-02-01 10:29 ` Marinescu, Bogdan A
2013-02-01 14:56 ` Richard Purdie
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=1368181932.11129.11.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@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