From: "Diego Elio Pettenò" <flameeyes@flameeyes.eu>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] libusb-compat preference in virtual/libusb:0 not strong enough?
Date: Mon, 11 Feb 2013 16:21:00 +0100 [thread overview]
Message-ID: <51190C5C.9000903@flameeyes.eu> (raw)
In-Reply-To: <20130211151728.2557.qmail@stuge.se>
On 11/02/2013 16:17, Peter Stuge wrote:
>> > Any idea on what's going on? BFS instead of DFS search when
>> > satisfying "||"?
> Seems a good explanation.. Can you try swapping the two in the virtual?
Or not.
--
Diego Elio Pettenò — Flameeyes
flameeyes@flameeyes.eu — http://blog.flameeyes.eu/
next prev parent reply other threads:[~2013-02-11 15:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 14:18 [gentoo-dev] libusb-compat preference in virtual/libusb:0 not strong enough? Maxim Kammerer
2013-02-11 15:17 ` Peter Stuge
2013-02-11 15:21 ` Diego Elio Pettenò [this message]
2013-02-11 16:44 ` Peter Stuge
2013-02-11 16:47 ` Diego Elio Pettenò
2013-02-11 16:54 ` Peter Stuge
2013-02-11 17:01 ` Diego Elio Pettenò
2013-02-11 17:09 ` Zac Medico
2013-02-11 17:22 ` Peter Stuge
2013-02-11 18:05 ` Maxim Kammerer
2013-02-12 0:37 ` Maxim Kammerer
2013-02-11 15:42 ` Maxim Kammerer
2013-02-11 15:47 ` Zac Medico
2013-02-11 15:40 ` Zac Medico
2013-02-11 16:04 ` Maxim Kammerer
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=51190C5C.9000903@flameeyes.eu \
--to=flameeyes@flameeyes.eu \
--cc=gentoo-dev@lists.gentoo.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