From: Robert Yang <liezhi.yang@windriver.com>
To: Martin Jansa <martin.jansa@gmail.com>,
"Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/9] file: 5.23 -> 5.24
Date: Wed, 29 Jul 2015 13:54:09 +0800 [thread overview]
Message-ID: <55B86A81.6090100@windriver.com> (raw)
In-Reply-To: <20150728134825.GB2465@jama>
On 07/28/2015 09:48 PM, Martin Jansa wrote:
> On Tue, Jul 28, 2015 at 02:08:20PM +0100, Burton, Ross wrote:
>> On 28 July 2015 at 03:12, Robert Yang <liezhi.yang@windriver.com> wrote:
>>
>>> * Use git repo rather than tarball since the original SRC_URI is not
>>> stable, it is not reachable sometimes.
>>>
>>
>> Personally speaking I see this as a recipe for a release of file which just
>> happens to use git to fetch the tarball (and presumably that hash is the
>> 5.24 tag). In situations like this I prefer to see the recipe called
>> file_5.24.bb as there's no point having a giant PV including git SHAs when
>> it's just the release.
>
> until someone sets SRCREV_pn-file = "${AUTOREV}" somewhere and git SHAs
> in PV suddenly gets very useful.
>
> Personally speaking I prefer recipes with git SCM in SRC_URI named
> <foo>_git.bb and PV set to "A.B.C+gitr${SRCPV}".
Thanks Ross and Martin, as Ross suggested, when the release is just 5.24,
not 5.24+some patches in the repo, I prefer name it as file_5.24.bb,
so the PV would be 5.24 which is more clear, I will update the patch.
// Robert
>
next prev parent reply other threads:[~2015-07-29 5:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 2:12 [PATCH 0/9] Packages Upgrade Robert Yang
2015-07-28 2:12 ` [PATCH 1/9] git: 2.4.4 -> 2.4.6 Robert Yang
2015-07-28 2:12 ` [PATCH 2/9] file: 5.23 -> 5.24 Robert Yang
2015-07-28 13:08 ` Burton, Ross
2015-07-28 13:48 ` Martin Jansa
2015-07-29 5:54 ` Robert Yang [this message]
2015-07-29 12:51 ` Richard Purdie
2015-07-28 2:12 ` [PATCH 3/9] libuser: 0.61 -> 0.62 Robert Yang
2015-07-28 2:12 ` [PATCH 4/9] less: 478 -> 479 Robert Yang
2015-07-28 2:12 ` [PATCH 5/9] cracklib: 2.9.4 -> 2.9.5 Robert Yang
2015-07-28 2:12 ` [PATCH 6/9] gnupg: 2.1.5 -> 2.1.6 Robert Yang
2015-07-28 2:12 ` [PATCH 7/9] help2man-native: 1.46.4 -> 1.47.1 Robert Yang
2015-07-28 2:12 ` [PATCH 8/9] man-pages: 4.00 -> 4.01 Robert Yang
2015-07-28 2:12 ` [PATCH 9/9] pax-utils: 1.0.3 -> 1.0.5 Robert Yang
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=55B86A81.6090100@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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.