From: Jerzy Grzegorek <jerzy.grzegorek@trzebnica.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4] bluez5_utils: new package
Date: Mon, 24 Mar 2014 00:10:00 +0100 [thread overview]
Message-ID: <532F69C8.5060202@trzebnica.net> (raw)
In-Reply-To: <532C6DDF.2090606@zacarias.com.ar>
Hi Gustavo, Marcin,
> On 03/21/2014 01:45 PM, Jerzy Grzegorek wrote:
>
>>> Hmm? bluez5 > bluez, and we care about visual name there (how it shows
>>> up in *config).
>> Don't compare bluez5 with bluez.
>> Compare bluez5_utils with bluez_utils.
>>
>> Regards,
>> Jerzy
> I know how sort works, i'm talking of common sense in this case.
> python is before python3, samba is before samba4 and so on, so in the
> bluez case the same would hold up, it's about context, not sort with lang=C.
> Regards.
Gustavo: Ah, yes, right. Sorry for this and thanks for your clarification.
Marcin: Sorry for the noise. Just don't take my comment into consideration.
Regards,
Jerzy
>
>
next prev parent reply other threads:[~2014-03-23 23:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 12:59 [Buildroot] [PATCH] bluez5_utils: new package Marcin Bis
2013-11-04 16:06 ` Thomas De Schampheleire
2013-11-04 21:34 ` [Buildroot] [PATCH v2] " Marcin Bis
2014-03-04 21:38 ` Yann E. MORIN
2014-03-20 13:48 ` [Buildroot] [PATCH v3] " Marcin Bis
2014-03-20 18:21 ` Thomas Petazzoni
2014-03-20 19:28 ` Jerzy Grzegorek
2014-03-21 9:48 ` Marcin Bis
2014-03-21 9:53 ` [Buildroot] [PATCH v4] " Marcin Bis
2014-03-21 11:08 ` Jerzy Grzegorek
2014-03-21 11:42 ` Gustavo Zacarias
2014-03-21 16:45 ` Jerzy Grzegorek
2014-03-21 16:50 ` Gustavo Zacarias
2014-03-23 23:10 ` Jerzy Grzegorek [this message]
2014-03-31 8:55 ` Marcin Bis
2014-03-31 8:58 ` [Buildroot] [PATCH v5] " Marcin Bis
2014-04-03 20:00 ` Thomas Petazzoni
2014-04-04 9:03 ` Marcin Bis
2014-08-02 11:08 ` Thomas Petazzoni
2014-03-21 16:55 ` [Buildroot] [PATCH v4] " Gustavo Zacarias
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=532F69C8.5060202@trzebnica.net \
--to=jerzy.grzegorek@trzebnica.net \
--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