Rasmus Lerdorf wrote:
Marcus Boerger wrote:
the solution is correct. And btw just another reason to switch to svn.
Without the patch the old branches magically inherit the new file just as
we could change the past.
I have applied the patch.
Thanks Rasmus, and Marcus for your analysis.
Marcus Boerger wrote:
the solution is correct. And btw just another reason to switch to svn.
Without the patch the old branches magically inherit the new file just as
we could change the past.
I have applied the patch. SVN has its own set of problems.
-Rasmus
--
PHP Internals - PHP Runtim
Jani Taskinen wrote:
Not that we will patch the repository files, but why do you care?
You actually use some old release branch? :)
In case I wasn't clear, or the patch wasn't clear, this is -every- historical
checkout that's broken. Including those in the past month.
>If you're
Hello Jani,
the solution is correct. And btw just another reason to switch to svn.
Without the patch the old branches magically inherit the new file just as
we could change the past.
best regards
marcus
Wednesday, December 7, 2005, 11:13:10 AM, you wrote:
> On Wed, 7 Dec 2005, Edin Kadribasi
On Wed, 7 Dec 2005, Edin Kadribasic wrote:
Jani Taskinen wrote:
Not that we will patch the repository files, but why do you care?
You actually use some old release branch? :)
I think that we should try to preserve the possiblity to checkout an old
version of PHP directly from the CV
Jani Taskinen wrote:
>
> Not that we will patch the repository files, but why do you care?
> You actually use some old release branch? :)
I think that we should try to preserve the possiblity to checkout an old
version of PHP directly from the CVS.
Edin
--
PHP Internals - PHP Runtime D
Not that we will patch the repository files, but why do you care?
You actually use some old release branch? :)
--Jani
On Wed, 7 Dec 2005, William A. Rowe, Jr. wrote:
Two weeks ago;
ext/pcre/config0.m4
was added by duplicating ext/pcre/config.m4,v directly in the CVS repository.
