From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] xenomai: bump version to 3.0.3
Date: Tue, 21 Mar 2017 10:19:01 +0100 [thread overview]
Message-ID: <20170321101901.1bfbc40e@free-electrons.com> (raw)
In-Reply-To: <7f8f513c-d847-5b70-c084-6538c3a6af43@mind.be>
Hello,
On Tue, 21 Mar 2017 09:57:35 +0100, Arnout Vandecappelle wrote:
> > My understanding was that Xenomai 3.x was significantly different from
> > Xenomai 2.x. Should we support both versions? Is Xenomai 3.x now old
> > enough that Xenomai 2.x is considered legacy? What problems will people
> > currently using Xenomai 2.x face if we ask them to move to Xenomai 3.x?
>
> There are some API differences, but (at least in dual-kernel mode), it is
> pretty easy to port over. I think we have lots of packages where version bumps
> introduce slight behavioural changes so I think this is OK.
OK, thanks. As long as it doesn't require people having Xenomai
applications to do a full rewrite, then I'm fine with a bump to 3.X as
opposed to supporting both 2.x and 3.x. Minor adaptations are OK, just
like is often needed when upgrading libraries, as you said.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-21 9:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 23:33 [Buildroot] [PATCH 1/3] xenomai: bump version to 3.0.3 sikor6 at gmail.com
2017-03-20 22:40 ` Thomas Petazzoni
2017-03-20 23:17 ` Paweł Sikora
2017-03-21 8:57 ` Arnout Vandecappelle
2017-03-21 9:19 ` Thomas Petazzoni [this message]
2017-03-21 17:39 ` Pawel Sikora
2017-03-20 23:33 ` [Buildroot] [PATCH 2/3] remove: 0001-bfin-remove-inline-keyword.patch sikor6 at gmail.com
2017-03-21 9:05 ` Arnout Vandecappelle
2017-03-21 15:53 ` Pawel Sikora
2017-03-20 23:33 ` [Buildroot] [PATCH 3/3] xenomai: enable SMP in configuration options sikor6 at gmail.com
2017-03-21 9:08 ` Arnout Vandecappelle
2017-03-21 15:57 ` Pawel Sikora
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=20170321101901.1bfbc40e@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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