All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4] bluez5_utils: new package
Date: Fri, 21 Mar 2014 13:55:34 -0300	[thread overview]
Message-ID: <532C6F06.9000407@zacarias.com.ar> (raw)
In-Reply-To: <532C6CC0.4070608@trzebnica.net>

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

Let me put it in exmaples, what if i make/add packages named bluezbeam,
bluezhack and a dozen more?
Regards.

      parent reply	other threads:[~2014-03-21 16:55 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
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                   ` Gustavo Zacarias [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=532C6F06.9000407@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.