[MLton-devel] accessing CVS commit log

[Stephen Weeks]

> Isn't everything under CVSROOT under CVS control? 

I don't think so.

> So, do you need to add the commitlogs2/mlton file? Of course, that
> would seem to suggest that you need to commit changes to it.  I
> guess avoid infinite regress in the comit logging script to not log
> commits of the commit log.

I guess that's one approach.  But all of the scripts that I see out
there on the web write directly to a file under CVSROOT, and as far as
I can tell CVS knows nothing about the file.  I guess CVS commit
synchronization makes that OK.

Anyways, I know that log_accum.pl is writing the file, because I can
add a line to maybe_log_accum that emails the file to me.  But that's
the only way I can directly access it -- to run a script as part of a
checkin that emails the file to me.  Blech.

I can also get the file out of the nightly tarball.  That might be
enough if I had a cron job do that and then post the file on
mlton.org.  But it sure would be nice to be able to read the file
directly.



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
MLton-devel mailing list
MLton-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mlton-devel