> I'm not so keen on this -- it's totally standard for README, INSTALL,
> COPYING, TODO, etc. to be in the top-level directory. Nobody will look
> for them in valgrind/docs/dist_files/.
sorry - I didn't explain this very well.
At build-time, FAQ.txt *also* gets generated from the xml, and put into
dist_files/. After the other formats are generated, the entire contents of
dist_files gets moved into the top-level dir valgrind/
> As for the FAQ, it's nice to have a copy of that in the top-level
> directory as well, in plain-text, if possible.
see above.
> > (tech docs)
> > - The design and implementation of valgrind (old)
> > - How cachegrind works
> > - Writing a new Valgrind Tool
> I'm not sure if the first two need to be in there any more. If they are,
> the first should definitely be marked at the top with a big "out of date,
> many details no longer true!" warning.
um, well, praps *all* the docs need a facelift?
> Is that the original XML, or the resulting HTML? It would be good to have
> both up for viewing.
This is just a tarball of files in .pdf, .ps and .html format so people can
get can idea of what it all comes out like.
d
|