From: Martin Jansa <martin.jansa@gmail.com>
To: Phil Blundell <philb@gnu.org>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] kernel.bbclass: use the same versioning schema for modules.tgz and provide link to latest
Date: Mon, 26 Nov 2012 19:18:10 +0100 [thread overview]
Message-ID: <20121126181810.GA18943@jama.jama.net> (raw)
In-Reply-To: <1353942076.13864.742.camel@phil-desktop>
[-- Attachment #1: Type: text/plain, Size: 776 bytes --]
On Mon, Nov 26, 2012 at 03:01:15PM +0000, Phil Blundell wrote:
> On Mon, 2012-11-26 at 14:57 +0100, Martin Jansa wrote:
> > I remember seeing some thread about making whole modules tarball
> > creation optional and disabled by default, so I guess there is only a
> > few users of this.
>
> That particular patch was apparently rejected, but I think you're right
> that only one or two people said at the time that they were using the
> tarball. It does seem to be a slightly fringe interest.
http://patches.openembedded.org/patch/37087/
Was it really rejected? I take RP's comment as rejecting setting
KERNEL_DEPLOY_MODULE_TARBALL to 0 as default, but not as rejecting whole
patch..
Cheers,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2012-11-26 18:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-22 12:46 [PATCH] kernel.bbclass: include PE in KERNEL_IMAGE_BASE_NAME Martin Jansa
2012-11-26 12:37 ` [PATCH] kernel.bbclass: use the same versioning schema for modules.tgz and provide link to latest Martin Jansa
2012-11-26 13:49 ` Bruce Ashfield
2012-11-26 13:57 ` Martin Jansa
2012-11-26 15:01 ` Phil Blundell
2012-11-26 18:18 ` Martin Jansa [this message]
2012-11-26 18:49 ` Bruce Ashfield
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=20121126181810.GA18943@jama.jama.net \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=philb@gnu.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