On Fri, 28 May 2010, Pierre Joye wrote:
> 2010/5/28 Johannes Schlüter :
>
> > Is anybody using this file? If this is thee case could somebody then
> > make sure it's being updated (and maybe take care of
> > ChangeLog-200[6-9].gz being created) else I'd suggest dropping them. An
> > outdated file
On Wed, 13 Oct 2004, Sascha Schumann wrote:
> That was an assert, not a fix.
>
> It appears to be a change in how cvs invokes the
> commitinfo/loginfo scripts. I will dig into the issue later,
> unless someone beats me to it.
I know they changed that in later CVS versions. Bu
That was an assert, not a fix.
It appears to be a change in how cvs invokes the
commitinfo/loginfo scripts. I will dig into the issue later,
unless someone beats me to it.
- Sascha
On Wed, 13 Oct 2004, Derick Rethans wrote:
On Tue, 12 Oct 2004, Andi Gutmans wrote:
It seems that
On Tue, 12 Oct 2004, Andi Gutmans wrote:
> It seems that everytime I commit to Zend CVS the commit message isn't sent
> out. For other's it works.
> It might be due to the warnings I'm getting. Does anyone have an idea what
> the problem could be?
Sascha was doing something with it, and committed
It seems that everytime I commit to Zend CVS the commit message isn't sent
out. For other's it works.
It might be due to the warnings I'm getting. Does anyone have an idea what
the problem could be?
Checking in zend_compile.c;
/repository/ZendEngine2/zend_compile.c,v <-- zend_compile.c
new rev