Hi,

As part of my threading/syncronization sanitization effort, I'd like to
extend/write some documentation describing
both the new changes and the existing infrastructure (of course code will be
commented as well).

I think this is a good chance to reorganize a bit our docs/ directory, and I
mean
- remove old/obsolete docs
- reorganize the subtree distinguishing user and tech docs

Example:

new layout: user documentation in docs/, devel-oriented docs in docs/tech/

cd transcode-CVS/docs
mkdir tech
mv architecture.txt LIBRARIES OPTIMIZERS *-API.txt ibp_support.txt
module-system-API.txt $ANYTHING_ELSE_I_FORGOT_HERE tech/
(update repositroy accordingly)

That will involve some directory creation and file move and that, as we
already know, will sadly drop the history.
(And that's the reason because I'm sending this mail instead just doing
that).
Someone mind of *this* history loss? I think that can be a tolerable loss.
If noone object, I'll go ahead quickly

Bests,

--
Francesco Romani

Reply via email to