Re: cvs: php4(php_4_0_4) / configure.in /main php_version.h
| From: | Andi Gutmans | Date: | Sun, 03 Dec 2000 19:37:18 +0000 |
| Subject: | Re: cvs: php4(php_4_0_4) / configure.in /main php_version.h | ||
| References: | 1 | Groups: | php.cvs |
| Request: | Send a blank email to php-cvs+get-2898@lists.php.net to get a copy of this message | ||
At 08:02 PM 12/3/00 +0100, Sascha Schumann wrote:
On Sun, 3 Dec 2000, Andi Gutmans wrote: At 19:48 03/12/00 +0100, Sascha Schumann wrote:They actual are very similar in CVS. Branches use a moving tag but I might be wrong.Sure there is. Before we run makedist we tag all three CVS trees.We've always spread the release CVS tags. It's the right thing to do.Well, there is a tag for RC3, but I'm not sure it is feasible to spread a virtual branch over two distinct CVS repositories..I'm talking about having a php_4_0_4 branch on cvs.zend.com. There is no precedence for that.Well, tags are fine, as I said above. All I'm saying is that there is no precedence for extending the branch from cvs.php.net to other repositories (which is not surprising, as this is the first time we use branches here). I guess you think branches and tags are equal, which they are not.
Uhm it's a bug fix which needs to get into 4.0.4 and his whitespace fixes
won't break anything. In any case, if you plan on manually applying it you
need to go through it filtering out the whitespace patches in your brain :)
I don't plan to apply it manually or to review obfuscated
patches. I'd appreciate it though, if Zeev or someone else
would post a patch containing only real changes, to give us a
chance to review it, _before_ committing it to the php_4_0_4
branch.
Whatever... I guess it's up to Zeev if he wants to start working on cleaning a diff or not. I had no problem looking at the commit he did in the main CVS tree.
Andi
---
Andi Gutmans <andi@zend.com>
http://www.zend.com/