From: Ian Murray <murrayie@yahoo.co.uk>
To: xen-devel@lists.xen.org, alex@alex.org.uk
Subject: Re: [Hackathon Minutes] Xen 4.4 Planning
Date: Fri, 14 Jun 2013 22:05:26 +0100 [thread overview]
Message-ID: <51BB8596.8080709@yahoo.co.uk> (raw)
In-Reply-To: <3DEF95228726EA7EFA8FF478@nimrod.local>
On 14/06/13 16:43, Alex Bligh wrote:
>
>
> --On 14 June 2013 14:55:07 +0100 Ian Campbell
> <Ian.Campbell@citrix.com> wrote:
>
>> I think you are totally out of order hounding Alex like this.
>
> Despite which, and despite there being no legal obligation to do so,
> we actually like publishing the open source stuff we do, and the
> fact it's not fantastically easy to find is well taken. I'm trying
> to find out who (hopefully someone internal) registered
> github.com/flexiant - if not I'll use something else - and we will
> be putting all our open source stuff up there, and have a link from
> the open source page in the manual and the open source page on
> the website. This plus at least one of those links should be up
> in the next few days.
>
> Note this is because we want to publish stuff, not because we
> think there is a compliance issue. Ian M: had you said "please
> could you publish this more obviously" you would have got the
> same response.
>
Thanks very much for that. As a casual browser, it will be a lot easier
than the repo. Absolutely no rush.
After reflecting on the conversation earlier, I realise it was
ill-conceived to take it in the direction I did, so please accept my
apologies for any distress that may have caused. Please also accept my
apologies if you felt "hounded" (granted, not your word). This wasn't my
intention.
Thanks again and have a good weekend.
Ian (M).
next prev parent reply other threads:[~2013-06-14 21:05 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 14:00 [Hackathon Minutes] Xen 4.4 Planning Lars Kurth
2013-06-13 14:22 ` Jan Beulich
2013-06-13 15:11 ` George Dunlap
2013-06-13 15:30 ` Jan Beulich
2013-06-13 15:39 ` Ian Campbell
2013-06-17 8:27 ` Fabio Fantoni
2013-06-17 9:52 ` Ian Campbell
2013-06-13 14:31 ` Ian Campbell
2013-06-13 14:52 ` George Dunlap
2013-06-13 15:06 ` Ian Campbell
2013-06-14 17:41 ` Konrad Rzeszutek Wilk
2013-06-13 14:43 ` George Dunlap
2013-06-13 17:09 ` Ben Guthro
2013-06-13 18:07 ` Pasi Kärkkäinen
2013-06-13 21:03 ` Alex Bligh
2013-06-13 23:56 ` Ian Murray
2013-06-14 7:01 ` Alex Bligh
2013-06-14 9:46 ` Ian Murray
2013-06-14 11:53 ` Alex Bligh
2013-06-14 12:32 ` Ian Murray
2013-06-14 12:49 ` Alex Bligh
2013-06-14 13:34 ` Ian Murray
2013-06-14 13:55 ` Ian Campbell
2013-06-14 14:44 ` Ian Murray
2013-06-14 14:55 ` Gordan Bobic
2013-06-14 15:00 ` George Dunlap
2013-06-14 15:09 ` Ian Campbell
2013-06-14 15:43 ` Alex Bligh
2013-06-14 21:05 ` Ian Murray [this message]
2013-06-19 21:22 ` Alex Bligh
2013-06-14 15:44 ` Alex Bligh
2013-06-14 17:25 ` Konrad Rzeszutek Wilk
2013-06-14 8:15 ` Jan Beulich
2013-06-14 9:47 ` George Dunlap
2013-06-14 9:59 ` Lars Kurth
2013-06-14 10:45 ` Jan Beulich
2013-06-14 11:19 ` George Dunlap
2013-06-14 11:30 ` Gordan Bobic
2013-06-14 12:10 ` Sander Eikelenboom
2013-06-14 10:44 ` George Dunlap
-- strict thread matches above, loose matches on Subject: below --
2013-06-14 11:46 Alex Bligh
2013-06-14 12:26 ` Jan Beulich
2013-06-14 12:45 ` Alex Bligh
2013-06-14 18:55 Alex Bligh
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=51BB8596.8080709@yahoo.co.uk \
--to=murrayie@yahoo.co.uk \
--cc=alex@alex.org.uk \
--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.