From: Ian Campbell <ian.campbell@citrix.com>
To: Doug Goldstein <cardoe@cardoe.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: xenbits GitHub mirror?
Date: Tue, 26 Jan 2016 16:55:40 +0000 [thread overview]
Message-ID: <1453827340.25257.47.camel@citrix.com> (raw)
In-Reply-To: <5675C368.9020601@cardoe.com>
On Sat, 2015-12-19 at 14:51 -0600, Doug Goldstein 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.
If forking the repo significantly easier than just creating an empty one of
your own and pushing to it? Is the parent repo "important" in some way in
the GH world? (Given that, as George says, we are unlikely to accept
contributions via GH pull requests etc).
Ian.
next prev parent reply other threads:[~2016-01-26 16:55 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 [this message]
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=1453827340.25257.47.camel@citrix.com \
--to=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 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.