LOGIN   :::   RECOVER PASS   :::   GET ACCOUNT    
Browse
  • Projects
  • Code (CVS)
  • Forums
  • News
  • Articles
  • Polls
  •  
    OpenCores
  • FAQ
  • CVS HowTo
  • Mission
  • Media
  • Tools
  • Sponsors
  • Mirrors
  • Logos
  • Contact us
  •  
    Tools
  • Search
      
  • Download Cores (CVSGet)
  •  
    More
  • Wishbone
  • Perlilog
  • EDA tools
  • OpenTech CD
  •  
    Navigation: All forums > Cores > Message List > Message Post

    Message

    Reply | Reply all
    Date Prev | Date Next | Thread Prev | Thread Next Date Index | Thread Index

    From: Jai Dhar<jai.dhar@g...>
    Date: Fri Apr 14 18:40:23 CEST 2006
    Subject: [oc] kindly convert opencores cvs repository to subversion (svn)
    Top
    There's no need to be rude; I'm not shoving anything down anyones
    "throaght" as you so eloquantly put it. It's a discussion, one that I
    didn't start - I offered my view on it and didn't knock anyones view
    who is against CVS, did I? If you couldn't care less, then don't voice
    your opinion.

    On 4/14/06, Gyorgy 'nog' Jeney <nog@s...> wrote:
    > Jai Dhar <jai.dhar@g...> wrote:
    > > I agree, doing everything at once is bad - and I didn't ever advocate
    > > that, I was merely speaking on the advantages of SVN. I also think
    > > having two repositories is bad. Why not setup a test repository for
    > > people to get used to? They can even move their own projects if they
    > > like. I don't think getting everyone to move their own projects will
    > > work (too messy), but in the meantime, while people are getting used
    > > to SVN, duplicate the CVS repo. into SVN.
    >
    > You're not advocating doing it wholesale..
    >
    > > Then, when people are ready,
    > > just point to the new location.
    >
    > ...But, actually you are! Realy, I don't see why you're trying to shove this
    > down everyone's throaght so badly. If devs want to move their projects, they
    > will and if they also leave the CVS repo behind, they'll get all the support
    > queries which is _their_ problem, not mine, not yours.
    >
    > > I'm not an expert on how to handle IT admin. stuff like this, so
    > > that's just one suggestion. But I do feel that you shouldn't hinder
    > > the introduction of a new and very beneficial technology when the only
    > > deterrant is inconvenience. If there were other detractors, like
    > > speed, complexity, cost etc.., then I would say convenience would play
    > > a part. But that's not the case with SVN.
    >
    > I'm not against it's introduction, I'm against doing it wholesale.
    >
    > > I guess it also comes down to two camps of thinking; those who feel
    > > that "if it ain't broke, don't fix it", and the opposite.. always
    > > pushing to the bleeding edge. Personally, I would like to think that
    > > somewhere in the middle is where I am - I waited a while for SVN to
    > > mature, and I tried it out even though CVS wasn't "broke". It only
    > > increased my productivity, which is always a good thing IMO.
    >
    > There _are_ two camps of thinking, just not the ones you mentioned. On one side
    > you have those that want to control everything and on the other you find those
    > who "couldn't care less". The later has a future, the former doesn't. Just let
    > both be and devs will use/convert to whichever suits them best at a time when it
    > suits them.
    >
    > > End of philosophical rant :)
    >
    > Same here :) Have a nice weekend.
    >
    > nog.
    > _______________________________________________
    > http://www.opencores.org/mailman/listinfo/cores
    >


    --
    Open-source hardware at http://www.fps-tech.net

     
    Copyright (c) 1999 OPENCORES.ORG. All rights reserved.