From: Joe MacDonald <joe@deserted.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-networking][PATCH] openflow: Add latest from git
Date: Thu, 5 Sep 2013 09:04:16 -0400 [thread overview]
Message-ID: <20130905130413.GF5086@deserted.net> (raw)
In-Reply-To: <CAJTo0LYA4pa_xSQe=PL9eYXfEr3rULSd7nJGSNLnoJKYEX_uMw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1431 bytes --]
[Re: [oe] [meta-networking][PATCH] openflow: Add latest from git] On 13.09.05 (Thu 10:01) Burton, Ross wrote:
> On 5 September 2013 05:39, Bruce Ashfield <bruce.ashfield@gmail.com> wrote:
> > The meta-virt recipe had the same _1.0.bb extension, and it's SRCREV lines up
> > with the openflow-1.0.0 tag in the repository:
> >
> > --------
> >
> > commit 5ccca75a69f99791659bcfbcf35353ab1921320a
> > Author: Glen Gibb <grg@stanford.edu>
> > Date: Thu Dec 31 16:00:53 2009 -0800
> >
> > docs: Update ChangeLog to include 1.0.0 information
> >
> > :100644 100644 2f13dd7... aa0e92e... M ChangeLog
> >
> > -------
> >
> > So it's definitely an option to keep that recipe around as the tagged 1.0, and
> > create a _git that tracks newer changes (where "newer" is relative, 2011 is
> > the latest commit in that repo).
>
> FWIW, I massively prefer "releases that are taken from git" like this
> (where its a git fetch on a hash that is the tag of the releases) to
> be versioned correctly like _1.0.bb instead of _git.bb for clarity and
> future alternatives such as true git snapshot or multiple versions.
Yeah, since the SRCREV in the _1.0.bb recipe actually corresponds to the
1.0 release tag, I'm in agreement. The proposed update from Laszlo also
now seems to justify having a _git.bb version, since it's pointing at a
(relatively) newer version of the recipe.
--
-Joe MacDonald.
:wq
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-09-05 13:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-02 8:20 [meta-networking][PATCH] openflow: Add latest from git Laszlo Papp
2013-09-03 1:56 ` Bruce Ashfield
2013-09-03 3:55 ` Laszlo Papp
2013-09-03 13:04 ` Bruce Ashfield
2013-09-03 13:13 ` Laszlo Papp
2013-09-03 13:38 ` Bruce Ashfield
2013-09-03 13:47 ` Laszlo Papp
2013-09-03 21:18 ` Joe MacDonald
2013-09-04 21:02 ` Joe MacDonald
2013-09-03 21:08 ` Joe MacDonald
2013-09-03 22:39 ` Bruce Ashfield
2013-09-04 3:27 ` Joe MacDonald
2013-09-04 12:22 ` Bruce Ashfield
2013-09-04 21:04 ` Joe MacDonald
2013-09-05 4:29 ` Bruce Ashfield
2013-09-04 13:13 ` Philip Balister
2013-09-04 13:31 ` Laszlo Papp
2013-09-04 20:26 ` Joe MacDonald
2013-09-04 21:14 ` Joe MacDonald
2013-09-05 4:39 ` Bruce Ashfield
2013-09-05 9:01 ` Burton, Ross
2013-09-05 9:13 ` Laszlo Papp
2013-09-05 13:04 ` Joe MacDonald [this message]
2013-09-05 13:07 ` Laszlo Papp
2013-09-05 13:01 ` Joe MacDonald
2013-09-05 5:05 ` Laszlo Papp
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=20130905130413.GF5086@deserted.net \
--to=joe@deserted.net \
--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.