Tickets :: Comment on [#2112] CVS Activity Log/Monitor

Search Results: 5 of 15 [ <<First <Prev Next> Last>> ] [ Return to Search Results ]

* Your Email Address
* Spam protection	Enter the letters below: .__ __. __ .__..___. \| \(__ / `[__] \| \|__/.__)\__.\| \| \|
Comment	>> All these features need cvs commits to be tracked on the cvs servers. > >> None of these tools is working on the repository alone afaik, which > >> is what Chora currently does. > > > > I'm looking closer at how CVSMonitor does their tracking, but this is > true for cvstrac - it has a line in the loginfo file in the CVSROOT > admin directory which prints out the relevant information ready for > parsing. I see this as the 'easiest' way to track checkins, > especially since chora doesn't support remote repositories currently. > If that is to change in the future, a different method would need to > be found (going back to using cvsps, likely) > > > > BTW, I'm having troubles with cvsps in chora for files right now... > but thats an issue for a different bug report :-)
Attachment
Watch this ticket