| |
|
 |
|
 |
|
|
|
| |
|
|
xen-merge
[Xen-merge] Re: Documentation for merge process (perish the thought! :-)
The *why* is what, at least in some places, I might have problems with.
Also, getting this as a by-product will be more efficient (in my
opinion) at the point where we're actually going to split things into
(logically consistent) patches. Hence I don't think I'll spend extra
time on this right now.
Jan
>>> "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
21.12.05 17:58:43 >>>
First, Jan, I want to acknowledge your excellent work so far.
I understand from similar experience on Xen/ia64 that this
work is very difficult, time-consuming, and -- though critical --
often unrewarded.
A suggestion: You are rapidly becoming an expert in what
it takes to port Linux to run on Xen. A useful by-product
of your effort would be to create a list of every difference
between Linux and Xenlinux along with WHY this difference
is necessary. This document would be exceedingly useful
when the effort commences to merge all of the changes upstream
and would also be helpful to future Linux (and other OS)
porters.
Dan
P.S. In the code, #ifdef CONFIG_XEN /* _crossref-number_ */
would be a good way to cross-ref the document.
_______________________________________________
Xen-merge mailing list
Xen-merge@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-merge
|
|
|
| |
|
Home