From: Martin Jansa <martin.jansa@gmail.com>
To: bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: bash-completion
Date: Sun, 21 Apr 2013 00:56:59 +0200 [thread overview]
Message-ID: <20130420225659.GM2489@jama> (raw)
[-- Attachment #1: Type: text/plain, Size: 410 bytes --]
There is old thread on oe-devel about it
http://lists.linuxtogo.org/pipermail/openembedded-devel/2007-December/003764.html
Is there any reason why it wasn't added to contrib yet?
Would it be applied if I send git patch adding it and update commands to
include cleansstate and packagedata + new options like -S and maybe
more?
Cheers,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next reply other threads:[~2013-04-20 23:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-20 22:56 Martin Jansa [this message]
2013-04-20 23:28 ` bash-completion Martin Jansa
2013-12-10 9:37 ` bash-completion Matthieu CRAPET
2013-12-10 14:35 ` bash-completion Martin Jansa
2013-12-13 8:49 ` bash-completion Matthieu CRAPET
2013-12-13 10:28 ` bash-completion Paul Eggleton
-- strict thread matches above, loose matches on Subject: below --
2019-09-26 23:16 bash-completion Slater, Joseph
2019-09-27 0:34 ` bash-completion Khem Raj
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=20130420225659.GM2489@jama \
--to=martin.jansa@gmail.com \
--cc=bitbake-devel@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 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.