On Sun, Aug 4, 2013 at 2:17 PM, Stephan Beal <[email protected]> wrote:
> Has anyone out there done any sort of time/effort/cost estimation > calculations based on fossil data? e.g. looking at the size of a change, or > maybe time span between closely-occurring commits, to estimate its "cost"? > Maybe running each version through sloccount and recording the SLOC diffs? > Here's a quick-hack bash script to do the latter: http://fossil.wanderinghorse.net/tmp/fsloc.sh.txt Usage: Start at an empty dir: [stephan@host:~/cvs/fossil/count]$ l total 148 drwxrwxr-x 2 stephan stephan 131072 Aug 4 14:59 . drwxrwxrwx 50 stephan stephan 16384 Aug 4 14:57 .. [stephan@host:~/cvs/fossil/count]$ Open a repo: [stephan@host:~/cvs/fossil/count]$ f open ../whprintf.fsl ... comment: More fixes/cleanups for string precision support. (user: stephan) checkins: 20 Run this script: [stephan@host:~/cvs/fossil/count]$ ../fsloc.sh Checkount #0: ad1d9b30 ==> _SLOC.00000.ad1d9b30 1127 top_dir ansic=1127 ... Checkount #18: 76371168 ==> _SLOC.00018.76371168 1042 top_dir ansic=1042 Checkount #19: f1bea87b ==> _SLOC.00019.f1bea87b sloccount failed. Presuming empty checkout and continuing. Done @ checkount #19: f1bea87b Output is in the files named _SLOC.* If all went well, the only files remaining in the current dir are _SLOC.* and .fslckout. If anyone has scripts for processing sloccount output i'd love to see them :). -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
