From: Artem Mygaiev <artem.mygaiev@globallogic.com>
To: Lars Kurth <lars.kurth@xen.org>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Dario Faggioli <dario.faggioli@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
David Vrabel <david.vrabel@citrix.com>,
Andrii Tseglytskyi <andrii.tseglytskyi@globallogic.com>
Subject: Re: [Need Input] (informal) Automotive PV drivers subproject request
Date: Tue, 10 Jun 2014 17:22:08 +0300 [thread overview]
Message-ID: <CALQdcALsH4c-=V47mzskv_7WoSffmTCj-Od7etH=0X66SWdYag@mail.gmail.com> (raw)
In-Reply-To: <5395B71F.8060707@xen.org>
[-- Attachment #1.1: Type: text/plain, Size: 1332 bytes --]
>
> So:
>>
>> * we need an official xenbits.org/pvdrivers.git repo; it would also come
>>> with its own mailing list if desired
>>> * in addition we need integration branches for xen.git, linux.git,
>>> pvdrivers.git - it appears that the consensus here is that we use the
>>> same pattern as elsewhere
>>>
>> Rather, we should have:
>>
>> xenbits.xen.org/automotive/pvdrivers.git
>> xenbits.xen.org/automotive/linux.git
>> xenbits.xen.org/automotive/xen.git
>> etc.
>>
>> (FSVO "automotive"; I currently have no opinion about the project
>> name.)
>>
> That would make sense. So we follow the convention xenbits.xen.org/<subproject
> name>/pvdrivers.git
>
I like the idea :)
However, if we allowed linux.git and xen.git in xenbits.xen.org/<subproject
> name>, it does increase the risk of creating a permanent fork (i.e. the
> main concerns raised by IanC, Stefano, etc.)
True. But this is always a risk (like with mentioned XenRT), even without
staging trees in subprojects. To me it is more a matter of maintainers'
and community discipline...
Artem Mygaiev | AVP - Delivery
GlobalLogic
P +380.44.4929695 ext.2023 M +380.67.9211131 S rosenkrantzguildenstern
www.globallogic.com
<http://www.globallogic.com/>
http://www.globallogic.com/email_disclaimer.txt
[-- Attachment #1.2: Type: text/html, Size: 4049 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-06-10 14:22 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 13:04 Automotive PV drivers project request Artem Mygaiev
2014-06-04 14:22 ` [Need Input] (informal) Automotive PV drivers subproject request Lars Kurth
2014-06-04 16:35 ` Dario Faggioli
2014-06-05 12:47 ` Artem Mygaiev
2014-06-05 13:32 ` Dario Faggioli
2014-06-06 8:59 ` Ian Campbell
2014-06-06 13:05 ` Lars Kurth
2014-06-06 15:08 ` Ian Campbell
2014-06-06 19:49 ` Artem Mygaiev
2014-06-06 22:01 ` Dario Faggioli
2014-06-09 10:18 ` Stefano Stabellini
2014-06-09 12:25 ` Lars Kurth
2014-06-09 12:30 ` Ian Campbell
2014-06-09 13:14 ` Lars Kurth
2014-06-09 12:37 ` Lars Kurth
2014-06-09 13:12 ` Ian Jackson
2014-06-09 13:31 ` Lars Kurth
2014-06-10 14:22 ` Artem Mygaiev [this message]
2014-06-10 14:51 ` Lars Kurth
2014-06-09 12:15 ` Lars Kurth
2014-06-11 11:37 ` Lars Kurth
2014-06-04 14:36 ` Automotive PV drivers project request Roger Pau Monné
2014-06-04 15:21 ` [Need Input] (informal) Automotive PV drivers subproject request Lars Kurth
2014-06-04 15:34 ` Roger Pau Monné
2014-06-05 13:07 ` Artem Mygaiev
2014-06-05 13:17 ` Automotive PV drivers project request David Vrabel
2014-06-05 13:22 ` Artem Mygaiev
2014-06-10 12:38 ` David Vrabel
2014-06-10 14:09 ` Lars Kurth
2014-06-10 14:18 ` Artem Mygaiev
2014-06-11 10:10 ` Stefano Stabellini
2014-06-11 15:08 ` Automotive PV drivers project request (need more input) Lars Kurth
2014-06-12 9:34 ` Stefano Stabellini
2014-06-12 13:43 ` Paul Durrant
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='CALQdcALsH4c-=V47mzskv_7WoSffmTCj-Od7etH=0X66SWdYag@mail.gmail.com' \
--to=artem.mygaiev@globallogic.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=andrii.tseglytskyi@globallogic.com \
--cc=dario.faggioli@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=lars.kurth@xen.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).