Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:2682
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Tue, 24 Jun 2003 08:26:50 +0200
To: internals@lists.php.net
Message-ID: <20030624062650.GA2899@gjat.josefine.at>
Mail-Followup-To: Markus Fischer <mfischer@gjat.josefine.at>,
	internals@lists.php.net
References: <Pine.LNX.4.53.0306240509480.32741@eco.foo> <5.1.0.14.2.20030624072449.0da0cea8@127.0.0.1>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5.1.0.14.2.20030624072449.0da0cea8@127.0.0.1>
User-Agent: Microsoft Outlook Express 5.50.4807.1700.314
Subject: Re: [PHP-DEV] Automated selection of engine
From: mfischer@gjat.josefine.at (Markus Fischer)

On Tue, Jun 24, 2003 at 07:28:40AM +0200, Andi Gutmans wrote : 
> However, I am not convinced that having to explicitly checkout the PHP_5 
> branch is such a good idea. I thought the idea was to have HEAD be the 
> current development version and branch if off when necessary. I would 
> prefer this kind of approach.

    I think the advantage of the requirement of the branch TAG is
    that commit messages now always identify themselves where
    they're comming from right within the subject.

    Commit messages until the change from Sascha were always
    named "[PHP-CVS] cvs: php4" though it was php5 really.

    Now they all look like "[PHP-CVS] cvs: php-src(PHP_5)" which
    imho is easier to identify were a single commit is comming
    from.

    This helps a lot if at a later stage you browser through
    commit mails; you don't need to keep track which version HEAD
    was at a given time; you simply read it in the subject.

    my 2c,

        - Markus