CVS heads-up

php.internals

William A. Rowe, Jr.

19 years ago
FYI, a cvs rtag -d php5_5_0 might be in order before somebody trips over this (if 5.2 ever evolves to 5.5, sort of unlikely but who knows?) Bill

Antony Dovgal

19 years ago
On 02/23/2007 11:31 PM, William A. Rowe, Jr. wrote:
> FYI, a cvs rtag -d php5_5_0 might be in order before somebody trips > over this (if 5.2 ever evolves to 5.5, sort of unlikely but who knows?)
?
-- Wbr, Antony Dovgal

William A. Rowe, Jr.

19 years ago
Antony Dovgal wrote:
> On 02/23/2007 11:31 PM, William A. Rowe, Jr. wrote: >> FYI, a cvs rtag -d php5_5_0 might be in order before somebody trips >> over this (if 5.2 ever evolves to 5.5, sort of unlikely but who knows?)
Was there ever such a release? There is such a tag hiding out there across php-src. (It's possibly hard to find because it's hiding in alot of the attic files, which is why I suggested rtag -d.) Unless, was there a purpose for tag (not branch) 5.5.0?

Antony Dovgal

19 years ago
On 02/24/2007 12:03 AM, William A. Rowe, Jr. wrote:
> Antony Dovgal wrote: >> On 02/23/2007 11:31 PM, William A. Rowe, Jr. wrote: >>> FYI, a cvs rtag -d php5_5_0 might be in order before somebody trips >>> over this (if 5.2 ever evolves to 5.5, sort of unlikely but who knows?) > > Was there ever such a release?
Apparently no.
> There is such a tag hiding out there across > php-src. (It's possibly hard to find because it's hiding in alot of the > attic files, which is why I suggested rtag -d.)
Does it do any harm?
> Unless, was there a purpose for tag (not branch) 5.5.0?
Probably somebody set this tag several years ago. Is this a problem?
-- Wbr, Antony Dovgal

William A. Rowe, Jr.

19 years ago
Antony Dovgal wrote:
> > Probably somebody set this tag several years ago. > Is this a problem?
Of course, if you are the person who goes to tag php5_5_0, which will blow up loudly, or almost silently if none of the current files have that tag but they sit in the attic. cvs co will pick them up in the later case quite quietly, and if you aren't paying attention, are delivered in the final tarball :)

Marcus Börger

19 years ago
Hello William, why? Simple cvs tag -F will do the trick. best regards marcus Friday, February 23, 2007, 10:16:33 PM, you wrote:
> Antony Dovgal wrote: >> >> Probably somebody set this tag several years ago. >> Is this a problem?
> Of course, if you are the person who goes to tag php5_5_0, which will > blow up loudly, or almost silently if none of the current files have that > tag but they sit in the attic. cvs co will pick them up in the later case > quite quietly, and if you aren't paying attention, are delivered in the > final tarball :)
Best regards, Marcus

William A. Rowe, Jr.

19 years ago
Marcus Boerger wrote:
> Hello William, > > why? Simple cvs tag -F will do the trick.
Nope - because -F doesn't remove tags, only overrides them. Ancient attic artifacts would remain tagged... Antony Dovgal wrote:
> > Well, we're not going to use in anyway, because it doesn't comply with > the naming standard we use: > php_x_x_x, not phpx_x_x.
Good point :)

Antony Dovgal

19 years ago
On 02/24/2007 12:16 AM, William A. Rowe, Jr. wrote:
> Antony Dovgal wrote: >> >> Probably somebody set this tag several years ago. >> Is this a problem? > > Of course, if you are the person who goes to tag php5_5_0, which will > blow up loudly
Well, we're not going to use in anyway, because it doesn't comply with the naming standard we use: php_x_x_x, not phpx_x_x.
> or almost silently if none of the current files have that > tag but they sit in the attic. cvs co will pick them up in the later case > quite quietly, and if you aren't paying attention, are delivered in the > final tarball :) >
-- Wbr, Antony Dovgal