Vimage commit

Julian Elischer julian at elischer.org
Mon Jun 9 23:11:10 UTC 2008


I have another branch in p4,
called vimage-commit

   //repos/projects/vimage-commit/src/sys/...

that currently is SUPPOSED to create an identical binary
to -current.

It contains A LARGE PART of the commits.
but only everything that compiles away to nothing if defined that way.

I always update vimage and vimage-commit together,
so that a diff between the two branches produces all the changes in 
vimage that do NOT just evaluate to nothing..


There is a perl script in the base called makemeat.pl produces such a 
diff.

so to recap:

   //repos/projects/vimage/...

is the tree that currently contains the full vimage diff.
It is derived from -current.
In the base directory is update.sh that keeps it merged with -current, 
and makediff.pl that generates a diff from -current.


   //repos/projects/vimage-commit/...

is the tree that currently contains the partial vimage diff that 
"evaluates to nothing".
It too is derived from -current.
In the base directory is update.sh that keeps it merged with -current, 
and makediff.pl that generates a diff from -current.
There is also a makemeat.pl that generates a diff between the two 
branches. This shows all the interesting stuff.





More information about the freebsd-virtualization mailing list