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: [oe-commits] Steve Sakoman : gnome-mplayer: bump SRCREV
Date: Thu, 26 Nov 2009 10:30:31 +0100	[thread overview]
Message-ID: <20091126093031.GA3354@jama> (raw)
In-Reply-To: <E1NDaYW-0003Fx-Nr@melo.openembedded.org>

On Thu, Nov 26, 2009 at 09:22:28AM +0000, git version control wrote:
> gnome-mplayer: bump SRCREV
> 
> ---
> 
>  recipes/gnome-mplayer/gnome-mplayer_svn.bb |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/recipes/gnome-mplayer/gnome-mplayer_svn.bb b/recipes/gnome-mplayer/gnome-mplayer_svn.bb
> index 5540f94..2769bcb 100644
> --- a/recipes/gnome-mplayer/gnome-mplayer_svn.bb
> +++ b/recipes/gnome-mplayer/gnome-mplayer_svn.bb
> @@ -1,7 +1,7 @@
>  require gnome-mplayer.inc
>  
> -SRCREV = "1569"
> -PV = "0.9.8+svnr${SRCPV}"
> +SRCREV = "1583"
> +PV = "0.9.8+svn${SRCPV}"

Did you remove 'r' intentionally or is it a typo?

I was trying to make svnr consistent in OE tree and only few recipes
were using svn without 'r'
http://cgit.openembedded.net/cgit.cgi/openembedded/commit/?id=6ca479d37af6d1e4e89e5dac0dc5b2fb81819c2b
if this isn't true:
* Should be safe as version svnr[1234567890]* > svn[1234567890]*
then I should fix more recipes

and if it is true then your srcrev bump won't be upgraded for people who
built gnome-mplayer between 6ca479d37af6d1e4e89e5dac0dc5b2fb81819c2b and
this change.

Cheers,

-- 
uin:136542059                jid:Martin.Jansa@gmail.com
Jansa Martin                 sip:jamasip@voip.wengo.fr 
JaMa                         



       reply	other threads:[~2009-11-26  9:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1NDaYW-0003Fx-Nr@melo.openembedded.org>
2009-11-26  9:30 ` Martin Jansa [this message]
2009-11-27 17:59   ` [oe-commits] Steve Sakoman : gnome-mplayer: bump SRCREV Steve Sakoman

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=20091126093031.GA3354@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.