From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-multimedia PATCH V2 1/6] gssdp: add 0.12.2.1 and 0.13.2
Date: Thu, 03 Jan 2013 11:00:32 +0000 [thread overview]
Message-ID: <3624723.LPVMAxKVvK@helios> (raw)
In-Reply-To: <CAJTo0LZNprjMsqdVH=xzcr_0TtJ1o9BF2sAjYyYJzViHw6Smvg@mail.gmail.com>
On Thursday 03 January 2013 10:26:35 Burton, Ross wrote:
> On 23 December 2012 19:44, Paul Eggleton <paul.eggleton@linux.intel.com>
wrote:
> > On Friday 21 December 2012 13:43:37 Ross Burton wrote:
> >> Signed-off-by: Ross Burton <ross.burton@intel.com>
> >
> > Why both versions?
>
> GUPnP uses the GNOME-style stable/development even/odd versioning so
> there's value in having both. Specifically, dLeyna requires the
> current development releases as that's where several critical bug
> fixes have landed (ideally those fixes would be pushed to the stable
> series, but I'm not in a position to suggest that anymore).
OK, I would definitely recommend noting that in the commit message in that
case.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2013-01-03 11:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-21 13:43 [meta-multimedia PATCH V2 1/6] gssdp: add 0.12.2.1 and 0.13.2 Ross Burton
2012-12-21 13:43 ` [meta-multimedia PATCH V2 2/6] gupnp: add 0.18.4 and 0.19.3 Ross Burton
2012-12-21 13:43 ` [meta-multimedia PATCH V2 3/6] gupnp-av: add 0.10.3 and 0.11.6 Ross Burton
2012-12-21 13:43 ` [meta-multimedia PATCH V2 4/6] gupnp-dlna: add 0.9.2 Ross Burton
2012-12-21 13:43 ` [meta-multimedia PATCH V2 5/6] gupnp-igd: add 0.2.2 Ross Burton
2012-12-21 13:43 ` [meta-multimedia PATCH V2 6/6] gupnp-tools: add 0.8.1 Ross Burton
2012-12-23 19:44 ` [meta-multimedia PATCH V2 1/6] gssdp: add 0.12.2.1 and 0.13.2 Paul Eggleton
2013-01-03 10:26 ` Burton, Ross
2013-01-03 11:00 ` Paul Eggleton [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=3624723.LPVMAxKVvK@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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