From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Michael D Labriola <mlabriol@gdeb.com>
Cc: xen-users-bounces@lists.xensource.com,
xen-devel@lists.xensource.com, xen-users@lists.xensource.com,
Dot Yet <dot.yet@gmail.com>
Subject: Re: Re: [Xen-users] Jeremy's git tags
Date: Fri, 12 Mar 2010 13:43:42 -0800 [thread overview]
Message-ID: <4B9AB58E.8020808@goop.org> (raw)
In-Reply-To: <OFC22AA0C8.2C330F38-ON852576E4.00719343-852576E4.0071F15F@gdeb.com>
On 03/12/2010 12:44 PM, Michael D Labriola wrote:
> idea how bad that would be.
>
Bad.
J
next prev parent reply other threads:[~2010-03-12 21:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <93bc4af41003112132g1566595ewc6371e7ac3816f69@mail.gmail.com>
[not found] ` <27874119.post@talk.nabble.com>
[not found] ` <93bc4af41003120431h2c839b3ep4d55b49567bfcd9e@mail.gmail.com>
2010-03-12 20:08 ` [Xen-users] Jeremy's git tags Dot Yet
2010-03-12 20:15 ` Martinx - ジェームズ
2010-03-13 8:12 ` Vincent Hanquez
2010-03-12 20:44 ` Michael D Labriola
2010-03-12 21:43 ` Jeremy Fitzhardinge [this message]
2010-03-12 21:45 ` [Xen-devel] " Jeremy Fitzhardinge
2010-03-13 2:31 ` Dot Yet
2010-03-13 9:42 ` Re: [Xen-users] " Sander Eikelenboom
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=4B9AB58E.8020808@goop.org \
--to=jeremy@goop.org \
--cc=dot.yet@gmail.com \
--cc=mlabriol@gdeb.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users-bounces@lists.xensource.com \
--cc=xen-users@lists.xensource.com \
/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.