Hi Hubert, On Friday, 2008-11-21 18:17:14 -0500, Hubert Figuiere wrote:
> > It might do better in future once the responsible person with > > permissions to edit the project switched the repository to SVN, but > > I have my doubts it will cope with our /cws/* structure, unless proven > > different.. > > With SVN it won't if you pull trunk for the code analysis, since merges > are attributed to the svn committer, unlike in git. Well, I don't know how Ohloh treats SVN repositories exactly today. With their IMHO clumsy approach to pull the repository (if that is still the case, I lost interest in monitoring their progress because there wasn't any) they probably can't do much better unless you tell them which branches to pull. Not a feasible procedure in our CWS scenario. CIA.vc does that nicely, it even allows you to setup a regex such that tags and CWS names show up as branches in the commit messages. Eike -- PGP/OpenPGP/GnuPG encrypted mail preferred in all private communication. Key ID: 0x293C05FD - 997A 4C60 CE41 0149 0DB3 9E96 2F1A D073 293C 05FD
pgpdRrPrke0XW.pgp
Description: PGP signature
