From: Jan Kiszka <jan.kiszka@siemens.com>
To: Philippe Gerum <rpm@xenomai.org>
Cc: "Xenomai@xenomai.org" <Xenomai@xenomai.org>
Subject: Re: [Xenomai] git://git.xenomai.org/ipipe.git reshuffle, 3.8.0 kernel support
Date: Tue, 11 Jun 2013 13:37:20 +0200 [thread overview]
Message-ID: <51B70BF0.9040904@siemens.com> (raw)
In-Reply-To: <51A39043.5010609@xenomai.org>
On 2013-05-27 18:56, Philippe Gerum wrote:
> On 05/27/2013 09:45 AM, Philippe Gerum wrote:
>>
>> The I-pipe tree at git://git.xenomai.org/ipipe.git will be reorganized
>> today at 3pm GMT. At this chance, support for the 3.8.0 kernel will be
>> introduced.
>>
>> The complete commit history will be preserved, along with existing tags.
>> Branches may be renamed though, to better reflect the new development
>> workflow introduced with the pipeline "core" series.
>>
>> If you have scripts pulling from this repository in any automated way,
>> you may want to stop them for the day.
>>
>> A description of the few changes involved will be sent to this mailing
>> list later today, shortly before the new repository is published.
>>
>
> The reshuffled repository is now on line.
>
> The changes are as follows:
>
> - all legacy pipeline branches (i.e. pre-"core" series) have moved under
> the legacy/ hierarchy, e.g.
> ipipe-2.6.20-powerpc => legacy/ipipe-2.6.20-powerpc
> All branches under legacy/ are frozen, and won't be updated anymore.
>
> - the master branch now reflects the state of the mainline I-pipe
> development. Pull from this branch for the latest validated commits, for
> the latest supported kernel.
>
> - new ipipe-<kernel.version> branches are started off master
> periodically, for maintaining the pipeline over stable kernel releases.
> These branches include the pipeline code for a given kernel release, for
> a set of architectures we support in this release. There is neither
> arch-specific nor -noarch branches anymore.
Will pulling in stable updates for a kernel major release create new
branches or is "ipipe-3.8.0" a misnomer that should actually be called
"ipipe-3.8"? I'd like to update 3.8 to the final stable release and was
wondering about the best process for this. We will need some core code
patch conflict resolutions that I already done here some time ago.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2013-06-11 11:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 7:45 [Xenomai] git://git.xenomai.org/ipipe.git reshuffle, 3.8.0 kernel support Philippe Gerum
2013-05-27 16:56 ` Philippe Gerum
2013-06-11 11:37 ` Jan Kiszka [this message]
2013-06-11 13:22 ` Philippe Gerum
2013-06-11 13:31 ` Jan Kiszka
2013-06-11 14:01 ` Philippe Gerum
2013-06-11 14:06 ` Jan Kiszka
2013-06-11 14:15 ` Philippe Gerum
2013-06-11 14:18 ` Jan Kiszka
2013-06-11 14:45 ` Philippe Gerum
2013-06-11 14:56 ` Jan Kiszka
2013-06-11 15:05 ` Philippe Gerum
2013-06-11 15:06 ` Jan Kiszka
2013-06-11 15:33 ` Philippe Gerum
2013-06-11 15:36 ` Jan Kiszka
2013-06-11 16:00 ` Jan Kiszka
2013-06-11 16:10 ` Philippe Gerum
2013-06-11 16:06 ` Philippe Gerum
2013-06-11 16:05 ` Jan Kiszka
2013-06-11 16:14 ` Philippe Gerum
2013-06-11 14:18 ` Philippe Gerum
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=51B70BF0.9040904@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=Xenomai@xenomai.org \
--cc=rpm@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.