[dev] Re: [cvs] commit: chora browse.php

Jan Schneider jan at horde.org
Sat May 29 01:21:43 PDT 2004


Zitat von Chuck Hagenbuch <chuck at horde.org>:

> Quoting Jan Schneider <jan at horde.org>:
>
>> Exactly. Because now, if you checkout CHORA_1_0 for example, there will be a
>> browse.php file that never was there. A more concrete problem will arise
>> when we release another stable Chora version. A version patch would then
>> try to delete a non-existing browse.php, causing the patch to fail.
>
> Okay. So I should remove the repo-copied browse.php and add a new 
> one, without
> the old cvs.php history, to the repo?

Yeah, that would cause less hassle. This is only necessary for files that
have been release tagged or branched before, but we already had some broken
version patches in the past for that reason.

Jan.

--
Do you need professional PHP or Horde consulting?
http://horde.org/consulting.php


More information about the dev mailing list