Hi list,
If after ... checkout php-src
I go to directory php-src and remove
ZendEngine2 directory, then run ... up -APd
don't restore this
directory from repo. How I can update my copy to repo status?
CVS client 1.11.20
Hi list,
If after
... checkout php-src
I go to directory php-src and remove
ZendEngine2 directory, then run... up -APd
don't restore this
directory from repo. How I can update my copy to repo status?
Do NOT remove the directory. buildconf handles this.
--Jani
>
>
>> Hi list,
>>
>> If after `... checkout php-src` I go to directory php-src and remove
>> ZendEngine2 directory, then run `... up -APd` don't restore this
>> directory from repo. How I can update my copy to repo status?
>
>
> Do NOT remove the directory. buildconf handles this.
>
> --Jani
>
I know that this directory is engine and it's nedded, but why it's not
recovered by `... ud -d`?
Pasha Zubkov
> Jani Taskinen wrote:
> >
> >
> >> Hi list,
> >>
> >> If after `... checkout php-src` I go to directory php-src and remove
> >> ZendEngine2 directory, then run `... up -APd` don't restore this
> >> directory from repo. How I can update my copy to repo status?
> >
> >
> > Do NOT remove the directory. buildconf handles this.
> >
> > --Jani
> >
>
> I know that this directory is engine and it's nedded, but why it's not
> recovered by `... ud -d`?
Re-read Jani's reply.
Do not touch anything, ./buildconf does it for you automagically.
--
Wbr,
Antony Dovgal
Antony Dovgal wrote:
Re-read Jani's reply.
Do not touch anything, ./buildconf does it for you automagically.
If I modified source, maybe delete some directories ;), and after this I
want to update source to repo status. "why it's not recovered by ... ud -d
?"
Antony Dovgal wrote:
Re-read Jani's reply.
Do not touch anything, ./buildconf does it for you automagically.If I modified source, maybe delete some directories ;), and after this I
want to update source to repo status. "why it's not recovered by... ud -d
?"
It's a CVS problem - it doesn't resolve repository links with upd, only
on checkout.
Derick
Derick Rethans wrote:
It's a CVS problem - it doesn't resolve repository links with upd, only
on checkout.Derick
Maybe sputid question, but why PHP stil use CVS instead of SVN?
Derick Rethans wrote:
It's a CVS problem - it doesn't resolve repository links with upd, only
on checkout.Maybe sputid question, but why PHP stil use CVS instead of SVN?
How do you want to convert 1100 users instantly without causing
disruptions?
Derick
Derick Rethans wrote:
Derick Rethans wrote:
It's a CVS problem - it doesn't resolve repository links with upd, only
on checkout.Maybe sputid question, but why PHP stil use CVS instead of SVN?
How do you want to convert 1100 users instantly without causing
disruptions?
magicwand.php
Derick
Pasha Zubkov wrote:
Derick Rethans wrote:
It's a CVS problem - it doesn't resolve repository links with upd, only
on checkout.Derick
Maybe sputid question, but why PHP stil use CVS instead of SVN?
Because CVS works and ppl are so far happy with it
Andrey
Andrey Hristov wrote:
Because CVS works and ppl are so far happy with it
Andrey
CVS don't always work properly. This example shows it ;) Also SVN has
better versioning control mechanism. Hope sometime in the future php
will "update" to SVN, so why not now?
CVS don't always work properly. This example shows it ;) Also SVN has
better versioning control mechanism. Hope sometime in the future php
will "update" to SVN, so why not now?
SVN has other annoyances. We will not move anytime soon. (period)
Derick
Andrey Hristov wrote:
Because CVS works and ppl are so far happy with it
Andrey
CVS don't always work properly. This example shows it ;) Also SVN has
It works fine as long as you don't try to outsmart it.
better versioning control mechanism. Hope sometime in the future php
SVN is far from better.
will "update" to SVN, so why not now?
Over my smoking carcass..
--Jani