Re: Source code control system

2008-02-19 Thread Shlomi Fish
On Tuesday 19 February 2008, Ohad Levy wrote: > what about git? > Well, my take on the problems with git are that: 1. Its Windows-support may be lacking. See: http://use.perl.org/~Alias/journal/33825 2. It is more complex than Subversion: << shlomi:~$ git- Display all 132 possibilities

Re: Source code control system

2008-02-19 Thread Shlomi Fish
On Tuesday 19 February 2008, Gilad Ben-Yossef wrote: > Ohad Levy wrote: > > what about git? > > Git main attraction is distributed development. For something like the > Linux kernel it is indispensable. > > The thing is, most software development, even in the Open Source world, > is not really dist

Re: Source code control system

2008-02-19 Thread Micha
On Mon, 18 Feb 2008 17:57:32 +0200 Shachar Shemesh <[EMAIL PROTECTED]> wrote: > Marc Volovic wrote: > > > Good heavens... > > > > Subversion and/or CVS - take your choice. > > > I'll go with that recommendation if you only give me one thing that CVS > does better than SVN. > > Between the tw

Re: Source code control system

2008-02-19 Thread Micha
On Tue, 19 Feb 2008 16:21:56 +0200 Gilad Ben-Yossef <[EMAIL PROTECTED]> wrote: > Ohad Levy wrote: > > what about git? > > > > Git main attraction is distributed development. For something like the > Linux kernel it is indispensable. > > The thing is, most software development, even in the Open

Re: Source code control system

2008-02-19 Thread Micha
svn (subversion) is relatively easy to use and has both gui and cli frontends (windows maybe only gui). there is tortoise svn which integrates into explorer. cvs is mostly the same. The big difference is that with cvs commits are per file (if you made dependent changes on two different files the

Re: Source code control system

2008-02-19 Thread Shlomi Fish
On Tuesday 19 February 2008, Shahar Dag wrote: > Hi > > the advantage of SVN over CVS is: > 1. if you commit several files, in SVN it is an atomic action while in CVS > it is not. Than mean that with CVS some file may be updated while other > wont ==> your repository is not consistent From what I

Re: Source code control system

2008-02-19 Thread Gilad Ben-Yossef
Ohad Levy wrote: what about git? Git main attraction is distributed development. For something like the Linux kernel it is indispensable. The thing is, most software development, even in the Open Source world, is not really distributed. Also, I don't think there is a Windows git client :-

Re: Source code control system

2008-02-19 Thread Marc Volovic
Oi, Git is a silly that. M - "Ohad Levy" <[EMAIL PROTECTED]> wrote: > what about git? > -- ---MAV Marc A. Volovic Swiftouch, LTD [EMAIL PROTECTED] +972-544-676764 ===

Re: Source code control system

2008-02-19 Thread Ohad Levy
what about git? On Feb 19, 2008 8:16 PM, Shahar Dag <[EMAIL PROTECTED]> wrote: > > > > Hi > > the advantage of SVN over CVS is: > 1. if you commit several files, in SVN it is an atomic action while in CVS > it is not. Than mean that with CVS some file may be updated while other > wont > ==> your

Re: Source code control system

2008-02-19 Thread Tzafrir Cohen
On Tue, Feb 19, 2008 at 02:16:39PM +0200, Shahar Dag wrote: > > > > Hi > > the advantage of SVN over CVS is: > 1. if you commit several files, in SVN it is an atomic action while in CVS > it is not. Than mean that with CVS some file may be updated while other > wont ==> your repository is not

Re: Source code control system

2008-02-19 Thread Shahar Dag
Hi the advantage of SVN over CVS is: 1. if you commit several files, in SVN it is an atomic action while in CVS it is not. Than mean that with CVS some file may be updated while other wont ==> your repository is not consistent 2. when renaming, CVS will loose the history while SVN whill han

Re: Source code control system

2008-02-18 Thread Geoff Shang
Shachar Shemesh wrote: I'll go with that recommendation if you only give me one thing that CVS does better than SVN. Between the two, I fail to find a single reason to prefer the former over the later. Well, given that subversion was written to be an improved replacement for CVS, it's unli

Re: Source code control system

2008-02-18 Thread Shachar Shemesh
Marc Volovic wrote: Good heavens... Subversion and/or CVS - take your choice. I'll go with that recommendation if you only give me one thing that CVS does better than SVN. Between the two, I fail to find a single reason to prefer the former over the later. Shachar

Re: Source code control system

2008-02-18 Thread Shlomi Fish
On Monday 18 February 2008, Maxim Kudelya wrote: > David Suna wrote: > > I am interested in setting up a simple source code control system for a > > SOHO setup. > > .. > > >Any suggestions? > > You could use Subversion (http://subversion.tigris.org/) as version > control system, > Trac (http://trac

Re: Source code control system

2008-02-18 Thread Marc Volovic
Good heavens... Subversion and/or CVS - take your choice. I am not sure what you mean by "graphic management", but both have graphic and web CLIENTS. Management is something completely different :-). Me = To unsubscribe, send

Re: Source code control system

2008-02-18 Thread Alex Dover
CVS or SVN are pretty straight forward. Most IDEs have integration with them. Both have nice windows shell extensions (TortoiseSVN/CVS) http://www.nongnu.org/cvs/ http://subversion.tigris.org/ Regards Alex Dover On Feb 18, 2008 3:50 PM, David Suna <[EMAIL PROTECTED]> wrote: > I am interested in

Re: Source code control system

2008-02-18 Thread Maxim Kudelya
David Suna wrote: I am interested in setting up a simple source code control system for a SOHO setup. .. Any suggestions? You could use Subversion (http://subversion.tigris.org/) as version control system, Trac (http://trac.edgewall.org/) as web-based front end and TortoiseSVN (http://tor