Dev book images are missing
dbn.lists at gmail.com
Fri Feb 9 10:50:11 PST 2007
On 2/9/07, M.Canales.es <macana at macana-es.com> wrote:
> Having the images in SVN have this pros, IMHO:
> - Make the sources more auto-contained
> - Avoid setting a Makefile envars and updating the XSL version number in
> - Also allow to use customized images, if dessired, and prevent to use newer
> upstream ones that might not have a good look for our book layout.
I would add "having version control" to that list. Having the images
in svn allows us to track the history of the images instead of being
tied to some external thing.
More information about the lfs-dev