From: Nivedita Singhvi <niv@us.ibm.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Robb Romans <FMJ@us.ibm.com>, xen-devel@lists.xensource.com
Subject: Re: [PATCH] Please pull xen-unstable-docs
Date: Thu, 10 Nov 2005 09:34:33 -0800 [thread overview]
Message-ID: <437384A9.5050004@us.ibm.com> (raw)
In-Reply-To: <130969488a62c0a27715b6f24774833f@cl.cam.ac.uk>
Keir Fraser wrote:
>
> On 10 Nov 2005, at 16:58, Robb Romans wrote:
>
>> Here are a few cleanups for the Users' Manual, including adding a
>> chapter on securing Xen from Anthony Liguori. This is also for testing
>> that I have done things correctly in using the separate doc tree.
>>
>> Please pull from http://xenbits.xensource.com/ext/xen-unstable-docs.hg
>
>
> Thanks! It would be more convenient to send small numbers of patches to
> the list, rather than pulling them from an external tree. I end up
> having to clone the tree, re-merge and do a diff to check what has
> actually been changed (since hg doesn't have good visualisation tools).
> It's worth it for trees that see plenty of activity like
> xen-unstable-ia64 -- it doesn't currently seem worthwhile for
> docuementation unless activity is going to ramp up significantly.
Hi Keir,
We had talked a bit with Ian about this much earlier, and
he had preferred a hg tree. We can always just push patches
out, too..We're going to start ramping up, and hope to put
out a steady stream of stuff over the next week, but it won't
be that kind of volume.
Let us know if you'd prefer the patches, instead.
thanks,
Nivedita
next prev parent reply other threads:[~2005-11-10 17:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-10 16:58 [PATCH] Please pull xen-unstable-docs Robb Romans
2005-11-10 17:15 ` Mark Williamson
2005-11-10 17:32 ` Dave Feustel
2005-11-10 17:35 ` Nivedita Singhvi
2005-11-10 17:35 ` Keir Fraser
2005-11-10 17:34 ` Nivedita Singhvi [this message]
2005-11-10 17:45 ` Keir Fraser
2005-11-10 18:02 ` Robb Romans
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=437384A9.5050004@us.ibm.com \
--to=niv@us.ibm.com \
--cc=FMJ@us.ibm.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@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.