On Mon, 2005-03-14 at 16:49 -0500, D. Hugh Redelmeier wrote:
> Any project that isn't tiny ought to use a repository to record
> changes ("source code control system", "version control system",
> "configuration management system" or whatever you want to call it).
>
> Such a repository is invaluable when you want to learn what changes
> were mand and why. It also helps in figuring out when a bug was fixed
> or introduced. Furthermore, if someone reports a problem with a
> previous release, you can use the repository to figure out what has
> been changed since then.
>
> ivtv used to use CVS on source forge. If you look on
> http://ivtv.sourceforge.net/ you will see CVS-Browser and other
> evidence. See also
> http://ivtv.writeme.ch/tiki-index.php?page=CvsCheckout
>
> Chris Kennedy has taken on maintainership of the code (my
> terminology). His fork(?) of the code is the one being actively
> developed. See
> http://ivtv.writeme.ch/tiki-index.php?page=DownloadIvyTv
>
> Chris:
>
> Are you using CVS (or something like it)? (I hope you are.)
>
> If so, can you make it publicly available? At least read-only?
>
> Is there a reason you don't want to use the sourceforge CVS?
>
> Thanks,
Beating a dead horse. You should search the archives.
>
> Hugh Redelmeier
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
ivtv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
