Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:39308
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 72.14.220.153 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=message-id:date:from:reply-to:to:subject:cc:in-reply-to
         :mime-version:content-type:references;
        b=YLi+LV3lcDJWHPsMpSHVdC2MXev6tJuBk25X/SmJYivepvbRxBqtBoE1b5YlWZsaVh
         NcAgv9zDhrkdtPvJQjYQJANiRL7hmo6htBBL11EX4/ZV4Tuq2lT7ZfDgqjoAwK/Bu8vz
         WRLC2xcDtDBod3TKN95yW8Cm/3n5zIirFlElI=
Message-ID: <10845a340807250215o26b80e88waae03f5429615a07@mail.gmail.com>
Date: Fri, 25 Jul 2008 10:15:11 +0100
Reply-To: RQuadling@GoogleMail.com
To: "Gwynne Raskind" <gwynne@wanderingknights.org>
Cc: "PHP Developers Mailing List" <internals@lists.php.net>
In-Reply-To: <40FEB6C9-9B66-4761-8B9C-0E70158D9962@wanderingknights.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_23362_29597294.1216977311494"
References: <40FEB6C9-9B66-4761-8B9C-0E70158D9962@wanderingknights.org>
Subject: Re: [PHP-DEV] CVS to SVN Migration
From: rquadling@googlemail.com ("Richard Quadling")

------=_Part_23362_29597294.1216977311494
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

2008/7/25 Gwynne Raskind <gwynne@wanderingknights.org>

> At this point it's clear that moving from CVS to SVN for PHP has become a
> more or less official project. As such, there is a new mailing list <
> svn-migration@lists.php.net> for anyone who wants to help with the move.
> If you're familiar with what I've already done so far (<
> http://wiki.php.net/svnmigration>) and want to help, I beg you on my knees
> to subscribe (send a mail to <svn-migration-subscribe@lists.php.net>) and
> let us know what you want to do :). It's past time for PHP to make this step
> a just a little bit further into the future and I hope we can work together
> to make it happen.
>
> -- Gwynne, Daughter of the Code
> "This whole world is an asylum for the incurable."
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
Hi.

I've been a client user of CVS (php) both SVN and git (strangely enough, for
the same project - PrototypeJS).

As a windows user my observations/opinions are ...

1 - CVS uses a version number for versions of a file and tags when branching
is necessary. From what I can tell a group of change to many files are not
grouped in any obvious way. TortoiseCVS integrates with the Windows Explorer
environment. Command line tools are provided as TortoiseCVS uses them
"behind the scenes". I've also got Cygwin's cvs.

2 - SVN uses a version number for versions of a file and uses directories
when branching is necessary. Groups of changes are connected via a
"changeset". TortoiseSVN integrates with the Windows Explorer environment in
a similar method to that of TortoiseCVS. I've also got Cygwin's svn.

3 - GIT uses a SHA1 hash to group the changes. I find this next to useless
to compare versions as there is no version number per se (at least not one I
can see). I've only got git-gui for Windows. It works very differently to
the Tortoise tools.


Purely from my own experience and knowledge level, I like SVN. I like the
idea of a group of changes being linked. I miss the version numbering (it
may just be that Prototype don't need them ...).

git feels very different to CSV and SVN. It may just be I need to change the
way I see the information provided.

If git can provide in-file version numbering (like CVS does), then that
would feel more comfortable than the SHA1 hashes used.

Richard.


-- 
-----
Richard Quadling
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731
"Standing on the shoulders of some very clever giants!"

------=_Part_23362_29597294.1216977311494--