Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [oe-commits] Koen Kooi : gstreamer-ti: bump to r126 to make gstreamer autoplug and playbin work
Date: Wed, 25 Feb 2009 10:06:50 +0100	[thread overview]
Message-ID: <go31na$n9l$1@ger.gmane.org> (raw)
In-Reply-To: <1235549128.2621.20.camel@andromeda>

On 25-02-09 09:05, Michael 'Mickey' Lauer wrote:
> Am Mittwoch, den 25.02.2009, 08:53 +0100 schrieb Koen Kooi:
>> On 24-02-09 23:05, Michael 'Mickey' Lauer wrote:
>>> Hi Koen,
>>>
>>>> -SRCREV = "121"
>>>> +SRCREV = "126"
>>> Is there any specific reason you're not using sane-srcrevs.inc for that?
>> The 5 minute reparse time everytime someone touches sane-srcrevs.
>
> Aha. I don't think that's a good reason, but YMMV. So we should get rid
> of sane-srcrevs.inc and put it all into the files?

It would make overriding revs a lot easier and handle things like 
multiple git kernels (e.g. linux-omap) and recipes with both svn and git 
versions (ffmpeg).
I have no strong opinions on dumping sane-srcrevs, but lately people 
have been willy-nilly updating revs that things are hardly 'sane' anymore.

regards,

Koen





      reply	other threads:[~2009-02-25  9:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090224211929.77E79E8037@amethyst.openembedded.net>
2009-02-24 22:05 ` [oe-commits] Koen Kooi : gstreamer-ti: bump to r126 to make gstreamer autoplug and playbin work Michael 'Mickey' Lauer
2009-02-25  7:53   ` Koen Kooi
2009-02-25  8:05     ` Michael 'Mickey' Lauer
2009-02-25  9:06       ` Koen Kooi [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='go31na$n9l$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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