xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Lars Kurth <lars.kurth@citrix.com>
To: George Dunlap <George.Dunlap@citrix.com>,
	Andrew Cooper <Andrew.Cooper3@citrix.com>
Cc: Doug Goldstein <cardoe@cardoe.com>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: xenbits GitHub mirror?
Date: Wed, 27 Jan 2016 15:18:10 +0000	[thread overview]
Message-ID: <D2CE8F3A.2512E%lars.kurth@citrix.com> (raw)
In-Reply-To: <CAFLBxZa5SO568sJwRHKU+BTZoTsBwaqj5BKhhpiFE-zn2SSocw@mail.gmail.com>


Sorry, I have been a little bit unresponsive. Things were a little hectic
in the last 2 weeks.


On 27/01/2016 11:21, "George Dunlap" <George.Dunlap@eu.citrix.com> wrote:

>
>> FWIW, I am +1 for setting up infrastructure like this, but lets do it
>> properly.
>>
>> Lars: Thoughts?

I don't mind if we had an official github mirror. In fact, it may make the
project a little bit more accessible to the younger crowd.
 

>Doug says that you can mark a repo as a 'mirror', which will prevent
>people from being able to send pull requests to it; so I think my
>technical objection has been answered.
>
>I think the idea is still only half-baked though, as I'm not sure how
>having a github mirror will make it so that most mail has a git repo
>you can pull from (which would be necessary to reach the ultimate
>goal, making it straightforward to apply patches sent to the list).


I would be good, if we could identify any workflow issues (e.g. such as
the mailing issue raised here). Maybe some of the people who have hands-on
experience with Github and mailing lists can make a few suggestions. We
then should also consider adding this to the How to submit patches wiki
page

Lars

  reply	other threads:[~2016-01-27 15:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-19 20:51 xenbits GitHub mirror? Doug Goldstein
2015-12-21 11:54 ` George Dunlap
2015-12-23  8:53   ` Jon Ludlam
2016-01-26 16:48     ` Doug Goldstein
2016-01-26 16:55 ` Ian Campbell
2016-01-26 17:26   ` Doug Goldstein
2016-01-26 22:36     ` Doug Goldstein
2016-01-27  9:34     ` George Dunlap
2016-01-27  9:44       ` Ian Campbell
2016-01-27  9:45     ` Ian Campbell
2016-01-27 10:55       ` Andrew Cooper
2016-01-27 11:21         ` George Dunlap
2016-01-27 15:18           ` Lars Kurth [this message]
2016-01-27 15:45             ` Ian Campbell
2016-01-27 16:01               ` George Dunlap
2016-01-27 16:14                 ` Ian Campbell
2016-02-03 15:38             ` Doug Goldstein

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=D2CE8F3A.2512E%lars.kurth@citrix.com \
    --to=lars.kurth@citrix.com \
    --cc=Andrew.Cooper3@citrix.com \
    --cc=George.Dunlap@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=cardoe@cardoe.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).