Re: Ada Reference Manual in texinfo format?

[Stephen Leake <stephen_leake@stephe-leake.org>]

"Ludovic Brenta" <ludovic@ludovic-brenta.org> writes:

> In that case, Stephe, you can host your scripts on Ada-France's
> monotone server if you like. Anything is better than email, IMHO :) 

In general, I agree that a real CM system is better than email. But
that's only if there is a requirement for sharing files in the first
place. I'm the only one working on these files at the moment. When I'm
done, I'll publish them, and you can copy them into the Debian
distribution.

They should _not_ need maintenance after that, but if they do, we'll
deal with it then. Again, it's only two files!

> PS. Monotone has a nice feature called "trust". You can set up hooks
> that will filter revisions based on who committed them (or other
> arbitrary criteria), and make them invisible to "update" and other
> commands if you don't trust these committers. A trusted committer can
> then "approve" a revision to make it visible. What's nice about it is
> that the "trust" feature is outside the database, and can be set up
> differently in each working copy; the database always contains all
> revisions, and each user can choose which revisions to trust.

I've finally decided I need to use a distributed CM system at work
(I've been using CVS). I'm looking into using 'git', mostly because
there is a Cygwin port for it, and the Linux kernel developers use it,
so I think it is well-supported. For a similar purpose (trusted vs
untrusted committers), they recommend using branches. Apparently it is
easy in git to synchronize two branches periodically.

That seems more straight-forward to me than the monotone trust
mechanism. But I'd have to actually use both on a real project to be
sure. Of course, I don't have the time for that :(.

-- 
-- Stephe