Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Adam Wozniak <awozniak@irobot.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] added new recipe for olsrd_0.5.6-r8
Date: Mon, 25 Jan 2010 08:51:32 -0800	[thread overview]
Message-ID: <4B5DCC14.3030509@irobot.com> (raw)
In-Reply-To: <201001251102.50572.holger+oe@freyther.de>

It is "revision" 8, not "release candidate" 8.  If you look at  
http://www.olsr.org/releases/0.5/ you'll notice they ALSO have things 
labeled 0.5.6-rcN, but these all predate 0.5.6-rN.  I think their 
numbering scheme through 0.5.6 is horrible.  It gets worse...  Four days 
after they posted 0.5.6-r8, they decided to break convention again and 
posted 0.5.6-r8-2 (and not 0.5.6-r9 as you'd expect).

It is indeed unfortunate.

--Adam

Holger Hans Peter Freyther wrote:
> On Saturday 23 January 2010 00:22:37 Adam Wozniak wrote:
>   
>> Sorry, I've tried and tried, but I can't get send-email to work (network
>> config settings which are completely out of my control).  Please try
>> this attachment.
>>     
>
> The upstream version number of "olsrd_0.5.6-r8" is a bit unfortunate. Is that 
> revision or release candidate 8? This also means that the generated OE package 
> will be something like olsrd-0.5.6-r8-rX".
>
> In case it is the release version it is probably fine but just a little bit 
> awkward, in case of rc we would have a small problem.
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>   




      reply	other threads:[~2010-01-25 16:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-19 22:55 [PATCH] added new recipe for olsrd_0.5.6-r8 Adam Wozniak
2010-01-21 22:47 ` Khem Raj
2010-01-22 23:22   ` Adam Wozniak
2010-01-23 14:15     ` Philip Balister
2010-01-25 10:02     ` Holger Hans Peter Freyther
2010-01-25 16:51       ` Adam Wozniak [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=4B5DCC14.3030509@irobot.com \
    --to=awozniak@irobot.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox