All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Ludlam <jonathan.ludlam@citrix.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: Doug Goldstein <cardoe@cardoe.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: xenbits GitHub mirror?
Date: Wed, 23 Dec 2015 08:53:01 +0000	[thread overview]
Message-ID: <20151223085301.GA1670@humongous.Belkin> (raw)
In-Reply-To: <CAFLBxZb+jZiX4YbnUdCDvy-oqd+chWSJht3w+WUgqs8khj5Vow@mail.gmail.com>

On Mon, Dec 21, 2015 at 11:54:52AM +0000, George Dunlap wrote:
> On Sat, Dec 19, 2015 at 8:51 PM, Doug Goldstein <cardoe@cardoe.com> wrote:
> > All,
> >
> > Now I'll start off by saying that "no" is a perfectly acceptable answer
> > to this suggestion. Basically I remember at the Xen Developer Summit a
> > few people mentioned it being nice if people provided a git tree where
> > their branches were available for testing. I was just thinking it might
> > be easier for third parties to do that if there was an official Xen
> > Project mirror of the main repos on xenbits on GitHub and people could
> > fork that repo and make their branch available. Just a thought.
> 
> So I don't think there would be any objection at all to individual
> contributors sending links to git repos that happened to be hosted on
> github in the cover letter of a patch series posted to xen-devel.
> 
> I also don't think there would be any objection to someone
> *unofficially* maintaining a xenbits mirror on github, and advertising
> its availability on the wiki, as long as it was clear that it was
> unofficial.
>

There's an unofficial mirror maintained by the Mirage team on the
under the mirage organization: https://github.com/mirage/xen

Jon

> I'll let someone who feels more strongly than I do comment on the
> ideological perspective of having an official mirror; but from a
> practical perspective, my concern would be dealing with people who
> clone it and then send pull requests.  I'm pretty sure we will never
> accept pull requests made via github, and as a policy we will
> therefore never look at pull requests.  Having dozens of open,
> un-answered pull requests on github will look bad for the project; and
> manually going through and rejecting every pull request with an
> explanation of why seems like a pain that I'd rather avoid if we can
> help it.
> 
>  -George
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  reply	other threads:[~2015-12-23  8:53 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 [this message]
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
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=20151223085301.GA1670@humongous.Belkin \
    --to=jonathan.ludlam@citrix.com \
    --cc=George.Dunlap@eu.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 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.