From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/7] kernel.bbclass: Ensure we have correct version information in deploy data
Date: Mon, 15 Apr 2013 15:46:51 +0100 [thread overview]
Message-ID: <1366037211.8670.50.camel@ted> (raw)
In-Reply-To: <20130415113853.GO2475@jama>
On Mon, 2013-04-15 at 13:38 +0200, Martin Jansa wrote:
> On Mon, Apr 15, 2013 at 12:07:01PM +0100, Richard Purdie wrote:
> > Currently the names used for the kernel in deploy will contain "AUTOREV"
>
> Here it shows "AUTOINC"
It should say AUTOINC in the commit message too...
Cheers,
Richard
prev parent reply other threads:[~2013-04-15 15:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 11:07 [PATCH 1/7] kernel.bbclass: Ensure we have correct version information in deploy data Richard Purdie
2013-04-15 11:07 ` [PATCH] recipes: Fix ALLOW_EMPTY with no package specified Richard Purdie
2013-04-15 11:43 ` Martin Jansa
2013-04-15 12:06 ` Richard Purdie
2013-04-15 11:07 ` [PATCH 2/7] update-alternatives: Ensure DEPENDS is correct in multilib case Richard Purdie
2013-04-15 11:07 ` [PATCH 3/7] ttf-bitstream-vera: Use fontcache class for postinstall Richard Purdie
2013-04-15 11:07 ` [PATCH 4/7] encodings: Set RDEPENDS correctly Richard Purdie
2013-04-15 11:07 ` [PATCH 5/7] qemuwrapper-cross: Inhibit default dependencies Richard Purdie
2013-04-15 11:07 ` [PATCH 6/7] nfs-export-root: Update to use packagegroup naming Richard Purdie
2013-04-15 11:07 ` [PATCH 7/7] allarch: Drop various problematic allarch usages Richard Purdie
2013-04-15 15:16 ` Mark Hatle
2013-04-15 15:40 ` Richard Purdie
2013-04-15 15:49 ` Mark Hatle
2013-04-15 16:15 ` Martin Jansa
2013-04-15 11:38 ` [PATCH 1/7] kernel.bbclass: Ensure we have correct version information in deploy data Martin Jansa
2013-04-15 14:46 ` Richard Purdie [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=1366037211.8670.50.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox