All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 2/2] sane-srcdates.inc: remove from all distro configs as well as file itself
Date: Tue, 30 Nov 2010 13:07:13 +0100	[thread overview]
Message-ID: <20101130120713.GH3387@jama> (raw)
In-Reply-To: <4CF4E21A.90009@opendreambox.org>

On Tue, Nov 30, 2010 at 12:38:02PM +0100, Andreas Oberritter wrote:
> Hello Martin,
> 
> On 11/30/2010 08:55 AM, Martin Jansa wrote:
> > * it's empty for > 6 months
> > * entries were moved to recipes
> > * SRCREV instead of SRCDATE is preferred anyways http://git.openembedded.org/cgit.cgi/bitbake/commit/?id=8da9744fcdf856abebcfbe9e3bc1b8cf07bc317b
> 
> > diff --git a/conf/distro/include/sane-srcrevs.inc b/conf/distro/include/sane-srcrevs.inc
> > index 5e5e121..2bfd038 100644
> > --- a/conf/distro/include/sane-srcrevs.inc
> > +++ b/conf/distro/include/sane-srcrevs.inc
> > @@ -2,4 +2,4 @@
> >  # only SRCREVs included in more recipes should be here, otherwise put sane SRCREV to recipe directly
> >  
> >  OPKG_SRCREV ?= "587"
> > -EFL_SRCREV ?= "55033"
> > +EFL_SRCREV ?= "55077"
> 
> this change doesn't seem to be related to the patch.

Ups, sure, won't be in pushed patch if someone ack it..

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com



  reply	other threads:[~2010-11-30 12:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-30  7:55 [PATCH 1/2] usermanual: update info with SRCPV, in recipe SRCREV and remove sane-srcdates Martin Jansa
2010-11-30  7:55 ` [PATCH 2/2] sane-srcdates.inc: remove from all distro configs as well as file itself Martin Jansa
2010-11-30 11:38   ` Andreas Oberritter
2010-11-30 12:07     ` Martin Jansa [this message]
2010-11-30 12:17     ` [PATCHv2] " Martin Jansa
2010-11-30 12:21       ` Andreas Oberritter
2010-11-30 23:46       ` Khem Raj

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=20101130120713.GH3387@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-devel@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 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.