Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:21069
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Wed, 7 Dec 2005 12:04:06 +0200 (EET)
Reply-To: Jani Taskinen <sniper@iki.fi>
To: "William A. Rowe, Jr." <wrowe@rowe-clan.net>
cc: internals@lists.php.net
In-Reply-To: <4396A35C.5050009@rowe-clan.net>
Message-ID: <Pine.LNX.4.61.0512071203310.1287@arfg.argcubovn.sv>
References: <4396A35C.5050009@rowe-clan.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Subject: Re: [PHP-DEV] CVS Repository Corruption
From: sniper@iki.fi (Jani Taskinen)


     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.
>
> Unfortunately this breaks every historical checkout, due to the now duplicate
> existance of config0.m4 and config.m4, causing duplicate builds of the pcre
> extention.
>
> Of course, if one wants to do this in order to preserve history, it's still
> essential to remove all prior tags from the new ,v file - to avoid exactly
> this sort of duplicate checkout -by tag-.  Of course checkouts by date would
> still check out duplicate files.
>
> And of course nobody wants the true history concealed by removing the old,
> now removed file from Attic/.  So the patch to the true config0.m4,v is
> attached for someone to modify this directly in cvs.  Note this is specific
> to today's untagged state, and within days this patch would become invalid
> when config0.m4,v is tagged with new, non- config.m4,v tags.
>
> Bill
>