Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Kuten <ivan.kuten@promwad.com>
To: buildroot@busybox.net
Subject: [Buildroot] Busybox minicom-like application?
Date: Wed, 24 Oct 2007 21:30:37 +0300	[thread overview]
Message-ID: <471F8F4D.6050202@promwad.com> (raw)
In-Reply-To: <1193180356.5708.1.camel@aeglos.sweden.atmel.com>

Ulf Samuelsson wrote:
> ons 2007-10-24 klockan 08:45 +1000 skrev Hamish Moffatt:
>> Jorge S. wrote:
>>> Yes, i know its there, but it gets HIDDEN when i select the "[*] Hide
>>> applications that are provided by busybox".
>>>
>>> Maybe there's a buildroot bug here?
>> busybox in SVN does have a microcom applet, as of four weeks ago. The
>> latest change to package/Config.in takes that into account.
>>
>> On Tue, Oct 23, 2007 at 11:04:10PM +0300, Ivan Kuten wrote:
>>> Indeed,
>>>
>>> see Config.in
>>>
>>> if !BR2_PACKAGE_BUSYBOX_HIDE_OTHERS
>>> source "package/microcom/Config.in"
>>> endif
>>>
> 
> I do not think that is a good idea to hide it until
> it is in the mainstream busybox.
> 

OK,

I will "unhide" it, and if microcom applet will be in busybox mainline then hide again.

BR,
Ivan
--------------------------------
Embedded Linux engineer,
Promwad Company: http://www.promwad.com/
Homepage : http://www.ivankuten.com/
--------------------------------

      parent reply	other threads:[~2007-10-24 18:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-23 18:32 [Buildroot] Busybox minicom-like application? Jorge S.
2007-10-23 19:49 ` Ivan Kuten
2007-10-23 18:52   ` Jorge S.
2007-10-23 20:04     ` Ivan Kuten
2007-10-23 22:45       ` Hamish Moffatt
2007-10-23 22:59         ` Ulf Samuelsson
2007-10-24 18:28           ` Ivan Kuten
2007-10-24 22:55             ` Ulf Samuelsson
2007-10-24 18:30           ` Ivan Kuten [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=471F8F4D.6050202@promwad.com \
    --to=ivan.kuten@promwad.com \
    --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