Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54436
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error)
To: RQuadling@GMail.com
Cc: David Soria Parra <dsp@php.net>, internals@lists.php.net
In-Reply-To: <CAKUjMCUirzSjVs7GvaZmWmhx2W=h6OGyOX0YKPnUHztRkZc5xQ@mail.gmail.com>
References: <slrnj3tulc.6vi.dsp@experimentalworks.net>
	 <CAKUjMCUirzSjVs7GvaZmWmhx2W=h6OGyOX0YKPnUHztRkZc5xQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Sun, 07 Aug 2011 23:21:15 +0200
Message-ID: <1312752075.2665.3.camel@guybrush>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Choosing a distributed version control system
 for PHP (or not). Call for Participation.
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Sun, 2011-08-07 at 22:13 +0100, Richard Quadling wrote:
> So, when someone like me comes along, someone capable of building the
> code and playing with it at a very minor level, I can be sure that if
> things don't work, it is probably me that's broke it and that I can
> rely on the branch to contain good working code. OK. I know ITRW,
> things do get left unfinished or plain broken. But it isn't as if the
> code belongs to a single person who may have not spent all their time
> with it.

you can fork it as you want on github (you can do that already btw.) but
you won't be able to push it on git.php.net (as you can't do know).

No real difference there.

Only difference is that code can be tracked and manged before reaching
php.net's main tree. There already inofficial versions out there,
sometimes containing "strange" patches. They are called "distribution
packages" - even harder to detect.

johannes