Groups > comp.lang.java.programmer > #32252

Re: Source Management

Path	csiph.com!usenet.pasdenom.info!aioe.org!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail
From	Martin Gregorie <martin@address-in-sig.invalid>
Newsgroups	comp.lang.java.programmer
Subject	Re: Source Management
Date	Mon, 3 Aug 2015 21:06:36 +0000 (UTC)
Organization	A noiseless patient Spider
Lines	74
Message-ID	<mpol4s$4gq$1@dont-email.me> (permalink)
References	<d3240fa5-2144-4dee-8249-62882bd6b02d@googlegroups.com>
Mime-Version	1.0
Content-Type	text/plain; charset=UTF-8
Content-Transfer-Encoding	8bit
Injection-Date	Mon, 3 Aug 2015 21:06:36 +0000 (UTC)
Injection-Info	mx02.eternal-september.org; posting-host="e5160e2be48f1ea550cf61512446f525"; logging-data="4634"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+1JKlB+0vFnn3Sk/LYW2Wvnc8qj1oK2qg="
User-Agent	Pan/0.139 (Sexual Chocolate; GIT bf56508 git://git.gnome.org/pan2)
Cancel-Lock	sha1:cOWJtbAhAe+TuhYbOBrGsjiDNgk=
Xref	csiph.com comp.lang.java.programmer:32252

Show key headers only | View raw

On Mon, 03 Aug 2015 08:00:17 -0700, e.d.programmer wrote:

> There was another thread discussing Sourceforge and github which was off
> topic so I started a new thread.
> What is a good offline source management software?  We're using
> SourceTree but either it needs a lot of configuration we can't figure
> out or it just plain sucks.
>
The only ones I've used are CVS, PVCS and git.

Comments:

CVS
--- 
This is widespread on *nix OSes. I've not seen it on Windows. Its biggest 
disadvantage is that version control is only at the individual file 
level: there's no facility for treating a group of files as a persistent 
commitment unit. Although it will let you commit a number of files at 
once and share the same commit description, this is merely a convenience 
and not a way of ensuring that the same group of files are permanently 
tied together as a persistent group that is always handled as, say, the 
set of sources that define a version of a program or system. Its biggest 
advantages are that its 'just there' on all *nixen and that, because all 
files and indexes are just text files in directories, you can fix any 
problems with a text editor, chown and chmod.

Because it maintains a single central repository, it can only be used 
offline if the repository is on a shared disk or is mounted on a single, 
multi-user computer.
 

PVCS
---- 
I've only used this on one project. Its a commercial Windows app that 
seemed to offer very similar capabilities to CVS including its use of a 
single, central repository.

GIT
---
I'm still learning about it. Since its a distributed system, every 
programmer with commitment rights has their own repository (in the .git 
directory of the directory tree where they hold the files for the project 
its managing. This means that it can be used offline except then a 
programmer is pushing his sources to the master repository and/or pulling 
changes out of the master repository. Changes to several files can be 
made into a commitment group, but, like CVS, this doesn't deem to have 
all that much significance when it comes to maintaining a large, long 
lasting system.

Other
-----
I have seen other version control systems that could and did use the 
concept of system versions to make horizontal slices across the vertical 
stack of versions of each individual file under its control. This meant 
that you could freeze a version (so the VCS kept a permanent picture of 
the production system while development of later versions continued) and 
then open a bug-fix version over that and the next development version 
above that. Why? well, for starters changes applied to the bug-fix 
version 'floated up' and would appear in the higher version(s) unless 
they had altered or removed the code that was affected by the bug.

I've always thought this was an excellent VCS, but unfortunately it was 
only ever implemented on a single mainframe OS whict I no longer use.
 
Anyway
------
I hope these comments help you select a suitable VCS.



-- 
martin@   | Martin Gregorie
gregorie. | Essex, UK
org       |

Thread

Source Management e.d.programmer@gmail.com - 2015-08-03 08:00 -0700
  Re: Source Management Cecil Westerhof <Cecil@decebal.nl> - 2015-08-03 18:04 +0200
    Re: Source Management e.d.programmer@gmail.com - 2015-08-03 12:08 -0700
      Re: Source Management leif.roar@dimnakorr.com - 2015-08-03 16:09 -0500
  Re: Source Management Eternal Hope <laughingspam99@gmail.com> - 2015-08-03 21:36 +0100
    Re: Source Management Martin Gregorie <martin@address-in-sig.invalid> - 2015-08-04 09:15 +0000
      Re: Source Management Eternal Hope <laughingspam99@gmail.com> - 2015-08-04 17:02 +0100
  Re: Source Management Martin Gregorie <martin@address-in-sig.invalid> - 2015-08-03 21:06 +0000
  Re: Source Management Arne Vajhøj <arne@vajhoej.dk> - 2015-08-03 21:10 -0400

csiph-web