Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54487
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain seld.be designates 209.85.215.42 as permitted sender)
Message-ID: <4E40E57C.70106@seld.be>
Date: Tue, 09 Aug 2011 09:45:00 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <slrnj3tulc.6vi.dsp@experimentalworks.net> <CAGSj+QuTc9g3yKuGQK6WKUkj7=-axNZaAAzT1-m9kSg_uX8pXQ@mail.gmail.com> <4E3F8915.8030009@rotorised.com>
In-Reply-To: <4E3F8915.8030009@rotorised.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Choosing a distributed version control system
 for PHP (or not). Call for Participation.
From: j.boggiano@seld.be (Jordi Boggiano)

On 08.08.2011 08:58, Ryan McCue wrote:
> Kiall Mac Innes wrote:
>> Later on in the doc, you go into detail about submodules, and CRLF -> LF
>> support in both Git and Hg.
> 
> To be fair, submodules don't work exactly the same. Unlike
> svn:externals, which are linked to a repository, submodules are linked
> to a repository *and a commit*. That means that if an external is
> updated, the submodule must be updated, and that change must be committed.

The main difference is that submodules are entire repositories, while in
svn you can take sub-trees as externals.

The difference you mention is not really one, because you can do the
same in svn using 'foo -r1000 svn://somerepo' and have it fixed to one
revision, just like git does. It's a much saner approach anyway to avoid
people having out-of-sync versions of the externals.

Cheers

-- 
Jordi Boggiano
@seldaek - http://nelm.io/jordi