Rafal Krzewski wrote:
Saving the bandwidth is definetely a good thing. I'm wondering if it is possible to avoid downloading a complete log file on each run. I imagine
that if you saved the login in ~/.statcvs along with a timestamp, and use a cvs log -D on the next run you could just combine the resulting
log ("delta") with the old log to get complete information, saving a lot
of bandwidth and server's procecssing time.
I've just realized that this is more complex than I thought. You can't combine cvs log output by concatenating. To take advantage of that the
revision information would have to be stored in a processed from, to
faciliate reading it, combining and storing again.
That's basically what the changelog patch I submitted does.
There are various options ranging from serialized Java objects through XML to a relational database, with XML looking the most promising IMO.
There is already an and CvsChangeLog command which produces xml formatted output (and probably does a lot of what the current changelog plugin does). But I doubt if this is currently compatible with statcvs - presumably it only uses a standard cvs log format. So you'd have to convert it back again. Probably the best place to push for changes like this is directly with the statcvs folk.
Luke.
-- Luke Taylor. Monkey Machine Ltd. PGP Key ID: 0x57E9523C http://www.monkeymachine.ltd.uk
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
