From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] __ipipe_root_status exported GPL only but used to be not GPL only and is breaking other code
Date: Wed, 10 Dec 2014 20:47:23 +0100 [thread overview]
Message-ID: <20141210194723.GW1524@hermes.click-hack.org> (raw)
In-Reply-To: <20141210193946.GG24110@csclub.uwaterloo.ca>
On Wed, Dec 10, 2014 at 02:39:46PM -0500, Lennart Sorensen wrote:
> On Wed, Dec 10, 2014 at 08:24:19PM +0100, Gilles Chanteperdrix wrote:
> > A false statement again: the I-pipe tree is just one tree with the
> > mainline changes merged from version to version. Granted, this is to
> > recent a change to solve the issue you have, but please do not
> > propagate false rumours.
>
> Well from my point of view it is a true statement. I ahve never yet
> found a git tree I could look at to see where the ipipe code changes
> came from. All I have ever located just has checkins of new versions
> at various points in time. I would love to actually be able to figure
> this out.
If you checkout
https://git.xenomai.org/ipipe.git/log/?h=raw-ipipe-3.16
You have all the changes that were made since we started working
with a unique tree. As for the change you are referring to, this is
not a change, as explained in the other answer I just sent.
--
Gilles.
next prev parent reply other threads:[~2014-12-10 19:47 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 18:37 [Xenomai] __ipipe_root_status exported GPL only but used to be not GPL only and is breaking other code Lennart Sorensen
2014-12-10 18:42 ` Gilles Chanteperdrix
2014-12-10 19:02 ` Lennart Sorensen
2014-12-10 19:04 ` Lennart Sorensen
2014-12-10 19:05 ` Gilles Chanteperdrix
2014-12-10 19:09 ` Lennart Sorensen
2014-12-10 19:11 ` Lennart Sorensen
2014-12-10 19:12 ` Gilles Chanteperdrix
2014-12-10 19:13 ` Gilles Chanteperdrix
2014-12-10 19:19 ` Lennart Sorensen
2014-12-10 19:24 ` Gilles Chanteperdrix
2014-12-10 19:39 ` Lennart Sorensen
2014-12-10 19:47 ` Gilles Chanteperdrix [this message]
2014-12-10 19:55 ` Lennart Sorensen
2014-12-10 19:59 ` Gilles Chanteperdrix
2014-12-10 20:05 ` Lennart Sorensen
2014-12-10 19:44 ` Gilles Chanteperdrix
2014-12-10 19:52 ` Lennart Sorensen
2014-12-10 19:57 ` Gilles Chanteperdrix
2014-12-10 20:12 ` Lennart Sorensen
2014-12-10 19:45 ` Philippe Gerum
2014-12-10 19:44 ` Lennart Sorensen
2014-12-10 20:13 ` Philippe Gerum
2014-12-10 20:11 ` Lennart Sorensen
2014-12-10 20:38 ` Philippe Gerum
2014-12-10 21:16 ` Lennart Sorensen
2014-12-10 21:23 ` Lennart Sorensen
2014-12-10 21:55 ` Jeff Webb
2014-12-10 22:01 ` Lennart Sorensen
2014-12-10 23:18 ` Jeff Webb
2014-12-10 20:53 ` Jeff Webb
2014-12-10 21:58 ` Gilles Chanteperdrix
2014-12-22 10:06 ` Jan Kiszka
2014-12-22 11:19 ` Philippe Gerum
2014-12-22 14:46 ` Lennart Sorensen
2014-12-22 15:00 ` Philippe Gerum
2014-12-22 19:08 ` Lennart Sorensen
2014-12-22 14:42 ` Lennart Sorensen
2014-12-22 14:44 ` Jan Kiszka
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=20141210194723.GW1524@hermes.click-hack.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=xenomai@xenomai.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.