From: Philippe Gerum <rpm@xenomai.org>
To: "florian.bezdeka@siemens.com" <florian.bezdeka@siemens.com>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>,
"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>,
"chensong@tj.kylinos.cn" <chensong@tj.kylinos.cn>
Subject: Re: Xenomai working branches for dovetail port / y2038
Date: Thu, 25 Feb 2021 14:42:37 +0100 [thread overview]
Message-ID: <875z2g8drm.fsf@xenomai.org> (raw)
In-Reply-To: <533af59b8fb4005eac8dae32084e742cea56ccaa.camel@siemens.com>
Hi Florian,
florian.bezdeka@siemens.com <florian.bezdeka@siemens.com> writes:
> Hi Philippe,
>
> could you please point me to your working branch / tree that you are
> using for the ongoing dovetail port? Or is it the wip/dovetail branch
> on the Denx gitlab instance [1]?
>
> Are we allowed, our is it possible that we get sufficient rights to use
> the same git repository / git tree that you are using? I guess that
> would simplify the workflow, but is not a must have...
My ongoing work on Xenomai+Dovetail is hosted at:
git://lab.xenomai.org/xenomai-rpm.git, branch for-upstream/dovetail
This is my personal tree. I can host more personal trees there if need
be.
>
> @Jan
> This is the second time that I'm facing some kind of "collaboration
> hurdles" in the Xenomai project. The first time (preparation of the
> y2038 roadmap) forced me to fork the gitlab project from the Denx
> gitlab instance to gitlab.com [2] to allow Song to easily contribute.
> Any plans / ideas to make collaboration easier?
>
> [1] https://gitlab.denx.de/Xenomai/xenomai/-/tree/wip/dovetail
> [2] https://gitlab.com/fbezdeka/xenomai
--
Philippe.
next prev parent reply other threads:[~2021-02-25 13:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 10:43 Xenomai working branches for dovetail port / y2038 florian.bezdeka
2021-02-25 13:42 ` Philippe Gerum [this message]
2021-02-25 13:48 ` Philippe Gerum
2021-02-25 13:56 ` 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=875z2g8drm.fsf@xenomai.org \
--to=rpm@xenomai.org \
--cc=chensong@tj.kylinos.cn \
--cc=florian.bezdeka@siemens.com \
--cc=jan.kiszka@siemens.com \
--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.