From: Philip Tricca <flihp@twobit.us>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: [meta-selinux] git recipes
Date: Sat, 27 Feb 2016 20:23:37 -0800 [thread overview]
Message-ID: <56D27649.4040306@twobit.us> (raw)
In-Reply-To: <56D274C6.90607@twobit.us>
Adding a sensible subject.
On 02/27/2016 08:17 PM, Philip Tricca wrote:
> While going through the backlog I ran across the 'git' versions of the
> user space. I noticed that a recent contribution was adding a patch to
> the git recipe and I figured that this patch would already be upstream
> and so wouldn't be necessary. Not so. The 'git' versions have SRCREV
> hard wired (SRCREV) to a commit id but it's way back from the end of
> 2013. They're also disabled via DEFAULT_PREFERENCE = "-1"
>
> These 'git' versions seem super useful for testing bleeding edge stuff
> so IMHO keeping them around would be the right thing to do. Not sure how
> I feel about them tracking an ancient commit though. Since they're never
> built by default it seems reasonable to track the master branch.
>
> What's our philosophy w/r to recipes that pull from git? Is there some
> history behind this SRCREV?
>
> Thanks,
> Philip
>
next prev parent reply other threads:[~2016-02-28 4:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-28 4:17 [meta-selinux] Philip Tricca
2016-02-28 4:23 ` Philip Tricca [this message]
2016-02-29 14:06 ` [meta-selinux] git recipes Mark Hatle
2016-03-01 18:30 ` Joe MacDonald
2016-03-02 5:40 ` Philip Tricca
-- strict thread matches above, loose matches on Subject: below --
2016-03-02 15:47 Radzykewycz, T (Radzy)
2016-03-03 3:59 ` Philip Tricca
2016-03-03 20:44 ` Joe MacDonald
2016-03-06 20:31 ` Philip Tricca
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=56D27649.4040306@twobit.us \
--to=flihp@twobit.us \
--cc=yocto@yoctoproject.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.