Re: GIT vs Other: Need argument
- From
Guilhem Bonnefille <guilhem.bonnefille@gmail.com>
- Date
- Apr 18, 2007, 12:40 UTC
- Message-ID
- <8b65902a0704180540l721b9b1dj6f6e068f0d7e5119@mail.gmail.com>
- In-Reply-To
- <200704171818.28256.andyparkins@gmail.com>
On 4/17/07, Andy Parkins <andyparkins@gmail.com> wrote:
Show 17 quoted lines
> On Tuesday 2007, April 17, Guilhem Bonnefille wrote: > > I'm new to Git, but completly crazy of it. > > > > In my point of view, in corporate team, lot of people does not > > want/need the power offered by Git. > > So, my conclusion is the better model in a corporate is a centralyzed > > repo with some users using Git as "frontend". Other people will > > simply use the native tools for accessing the repo. > > Git has you covered there - it works better than other version control > systems for that model too. I do it all the time; the only difference > is that with git it's not the tool doesn't force the choice on you. > > If you want a central repo, just make one - designate one repository as > central, put it in the .git/config file for each of the others and away > you go. Pretend it's centralised if you want; you and your colleagues > need never know otherwise.
In fact, the most important problem (in my case) is that there are people that really don't want/need Git features. These people consider that CVS/SVN are constraints and not usefull tools. They are not interested in what a VCS can offer. I have success with CVS/SVN because we now use Eclipse which offers an easy to use GUI for CVS/SVN actions. An other point is that CVS/SVN actions for our developers are "trivial": update or commit, nothing more (even tags are made by "power" users, so working with branches...). With Git, you have to ALWAYS remember that you have a repo locally which is different than the central repo. I think this point is quite confusing for people not interested in the features offered by having a "private" repo.
This is why I think my corporate friends will brake if I try to propose Git for everybody.
In my mind, git-svn or even git-svnserve, are THE tools to introduce Git in teams not convinced by the power of DVCS. Or perhaps someone will create a porcelain that offers the same simple interface of CVS/SVN and will integrate it in all the fantastic IDE ;-)
-- Guilhem BONNEFILLE -=- #UIN: 15146515 JID: guyou@im.apinc.org MSN: guilhem_bonnefille@hotmail.com -=- mailto:guilhem.bonnefille@gmail.com -=- http://nathguil.free.fr/