WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Xen 3.0 documentation changes

To: Robb Romans <FMJ@xxxxxxxxxx>
Subject: Re: [Xen-devel] Xen 3.0 documentation changes
From: Steven Hand <Steven.Hand@xxxxxxxxxxxx>
Date: Wed, 07 Dec 2005 18:00:06 +0000
Cc: Xen Devel List <xen-devel@xxxxxxxxxxxxxxxxxxx>, Steven Hand <Steven.Hand@xxxxxxxxxxxx>
Delivery-date: Wed, 07 Dec 2005 18:00:54 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: Message from Robb Romans <FMJ@xxxxxxxxxx> of "Wed, 07 Dec 2005 11:44:24 CST." <873bl4redj.fsf@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> >>>>> "SH" == Steven Hand <Steven.Hand@xxxxxxxxxxxx> writes:
> 
>     >> Checking the changelog today for xen-unstable.hg, I find that
>     >> some of the work that IBM has contributed to the Users' Manual
>     >> and Interface Manual has been discarded.
> 
>     SH> Which work are you referring to?
> 
> :)
> 
> For example, the Users' Manual is now one 74K file. There was agreement
> between us and Xen to break it into smaller chunks, and we spent the
> time to do that.

Yes, I moved it (and the interface manual) back into one file to more 
easily enable spell checking etc. It doesn't seem that there's much 
benefit in having lots of small files - hg is fine with merges and 
patches to parts of text files. 

Are you keen to re-break it apart? I could understand if there were  
lots of discrete edits taking place in various and an inability to 
use merge but surely this is not the case? 


>     >> Would someone from Xen please be kind enough to explain why this
>     >> happened?
> 
>     SH> Prior to the release we tidied up the documentation to make it
>     SH> at least consistent/correct (as far as possible). It may be that
>     SH> this involved removing some of your text - but cannot say as I'm
>     SH> not aware what your text was (see above).
> 
> It is not "my text". It is work done by IBM that was accepted into the
> tree.

Understood. 

> The changes I'm referring to appear to have happened after the
> release. My guess is that is a consequence of your internal tree being
> pushed out to the open source tree.

Yes, sorry - I checked it into our internal staging tree which then 
took a little while to be pushed publically (since we run regression
tests before a push to ensure the tree is not badly broken). 

> [8305: Xen patchbot -unstable ] [Xen-changelog] Updated docs for Xen
> 3.0.
> From: Xen patchbot -unstable <patchbot-unstable@xxxxxxxxxxxxxxxxxxx>
> Subject: [Xen-changelog] Updated docs for Xen 3.0.
> To: xen-changelog@xxxxxxxxxxxxxxxxxxx
> Date: Tue, 06 Dec 2005 17:52:14 +0000
> Reply-To: xen-devel@xxxxxxxxxxxxxxxxxxx
> 
> # HG changeset patch
> # User smh22@xxxxxxxxxxxxxxxxxxxx
> # Node ID c8fdb0caa77b429cf47f9707926e83947778cb48
> # Parent  0255f48b757fc4a69846356e8f42e9a4ed410c8c
> Updated docs for Xen 3.0.
> 
> Signed-off-by: Steven Hand <steven@xxxxxxxxxxxxx>
> <snip>
> 
>     >> What is the status of the patch that I submitted on Monday?
> 
>     SH> The patch you submitted on Monday was against an older version
>     SH> of the tree and has not yet been applied.
> 
> It wasn't an older version when it was submitted.

True - my bad. 

I've merged and applied it to the staging tree - should be pushed 
out soon.


cheers,

S.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>