Date: Mon, 09 Jun 2008 16:11:08 -0700 From: Julian Elischer <julian@elischer.org> To: James Gritton <jamie@gritton.org> Cc: freebsd-virtualization@freebsd.org Subject: Vimage commit Message-ID: <484DB88C.1020403@elischer.org> In-Reply-To: <484DACBD.50109@gritton.org> References: <484CC690.9020303@elischer.org> <20080609174826.Q83875@maildrop.int.zabbadoz.net> <484D8EDD.3040103@elischer.org> <484DA546.9060005@gritton.org> <484DAB87.6040706@elischer.org> <484DACBD.50109@gritton.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?484DB88C.1020403>