Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:58567
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain stefan-marr.de from 81.20.134.149 cause and error)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <slrnjl54vo.mfm.dsp@experimentalworks.net>
Date: Sun, 4 Mar 2012 14:09:02 +0100
Cc: internals@lists.php.net
Content-Transfer-Encoding: quoted-printable
Message-ID: <0BDFACD9-97EA-47CC-B570-6BF20594AF95@stefan-marr.de>
References: <slrnjl54vo.mfm.dsp@experimentalworks.net>
To: David Soria Parra <dsp@php.net>
Subject: Re: [PHP-DEV] Git Migration: Status Update
From: php@stefan-marr.de (Stefan Marr)

Hi David:

On 03 Mar 2012, at 22:58, David Soria Parra wrote:

> (1) Pull requests on github.com go to the git-pull mailinglist.
>     Make sure you subscribe to it.
> (2) Johannes is working on an interface that allows people with
>     valid PHP user accounts to close pull requests.
> (2) Fix the bugsweb integration, so that references to bugs inside
>     the commits will work. Florian is working on it.
> (4) FAQ

Will there be an integration with pull requests and the bug tracker, or =
remains attaching patches the preferred way?=20

What is the new preferred replacement for a sparse SVN checkout + single =
commit per change? As I understand it, currently, we try to have a =
single commit for all branches (PHP_5_n, and trunk). How is that =
supposed to be done with git?
=46rom reading https://wiki.php.net/rfc/dvcs#workflows, I assume, all =
branches need to receive separate commits + pushes?

Thanks
Stefan


--=20
Stefan Marr
Software Languages Lab
Vrije Universiteit Brussel
Pleinlaan 2 / B-1050 Brussels / Belgium
http://soft.vub.ac.be/~smarr
Phone: +32 2 629 2974
Fax:   +32 2 629 3525