Re: [Obo-discuss] Sourceforge CVS URLs changed

[Tim C. <ti...@ml...>]

I am curious to know if you have considered moving to GIT?
Wouldn't it be a more appropriate model?

--Tim

On Tue, Dec 4, 2012 at 8:16 PM, Chris Mungall <cjm...@lb...> wrote:

> For users of sourceforge CVS - the viewvc URLs have changed.
>
> Whereeas previously you would have used a URL such as:
>
>
> http://obo.cvs.sourceforge.net/viewvc/obo/obo/ontology/phenotype/mammalian_phenotype.obo?view=log
>
> You should now use
>
>
> http://obo.cvs.sourceforge.net/viewvc/obo/obo/obo/ontology/phenotype/mammalian_phenotype.obo?view=log
>
> It's not clear why this change happened, we're following up with SF.
>
> Note to ontology providers: we recommend using a version control system
> other than CVS. SVN is probably best for most people. We can provide
> assistance with setting up a repository.
>
> Note to ontology consumers: we don't recommend bookmarking viewvc URLs for
> ontologies. Ontology providers can and do change their version control
> systems. Most of the OBO library ontologies can now be resolved via purls.
> E.g.
>
>         http://purl.obolibrary.org/obo/cl.owl
>         http://purl.obolibrary.org/obo/cl.obo
>
> We recommend using these in applications
>
>
>
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> Obo-discuss mailing list
> Obo...@li...
> https://lists.sourceforge.net/lists/listinfo/obo-discuss
>



-- 
============================================
Timothy Cook, MSc           +55 21 94711995
MLHIM http://www.mlhim.org
Like Us on FB: https://www.facebook.com/mlhim2
Circle us on G+: http://goo.gl/44EV5
Google Scholar: http://goo.gl/MMZ1o
LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook