If anybody is willing to do so, he'll get svn write access so feel
free
to volounteer ;)
I am maybe interested in doing so - if I am bright enough to do it. :-)
helmut
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
Jonas Maebe schrieb:
I think such updating could in fact be perfectly done by
someone else than the core developers. In general you don't need
intricate knowledge of the compiler or other things. Before committing,
just check whether everything still compiles after merging and whether
there
On Wednesday 08 November 2006 10.25, Jonas Maebe wrote:
On 8 nov 2006, at 06:52, Martin Schreiber wrote:
But what should we do if we can't use trunk because it is not
stable and we
can't use 2.0.4 because it is buggy?
There will *always* be bugs in the latest release which cause it not
On 8 nov 2006, at 11:47, Martin Schreiber wrote:
There will *always* be bugs in the latest release which cause it not
to work for some people. If we'd release a 2.0.6, that situation
would not change and some of those people would also think that their
bug is so important it requires a new
Is it possible to backport the resolution of 0007281 from
head to fixes branch?
Best Regards, helmut
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
Is it possible to backport the resolution of 0007281 from head to fixes
branch?
It is not usefull to do. There won't be a new release anymore from the
fixes branch.
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
Helmut Hartl schrieb:
It is not usefull to do. There won't be a new release anymore from the
fixes branch.
What Peter wanted to say is: there won't be any 2.0.x releases but we
want the next release to be 2.2.0 instead.
Your statement concludes that 2.04 is not usable for production
Florian Klaempfl schrieb:
I merged the patch
Well, actually commit is running :)
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
It is not usefull to do. There won't be a new release anymore from the
fixes branch.
What Peter wanted to say is: there won't be any 2.0.x releases but we
want
the next release to be 2.2.0 instead.
Does that mean we can soon expect single static assignment?
SSA is only partly implemented.
It is not usefull to do. There won't be a new release anymore from the
fixes branch.
Your statement concludes that 2.04 is not usable for production
environment.
- Except you do not use interfaces - or write programs which are only
commandlinetools, not expected to run for some time.
This
On 07 Nov 2006, at 23:08, Peter Vreman wrote:
Does that mean we can soon expect single static assignment?
SSA is only partly implemented. Unless you are running a scientific
benchmark you won't notice it.
It's actually (partial) static single use which we have. But other
optimizations to
Florian Klaempfl schrieb:
I merged the patch but help us to test 2.1.1 as much as possible
based
on the revisions known to be good
(http://www.freepascal.org/wiki/index.php/Tested_Unstable_Revisions)
so
we can get 2.2.0 out asap (head is currently broken due to heavy
rewrites).
Thank
On Tuesday 07 November 2006 17.46, Peter Vreman wrote:
Is it possible to backport the resolution of 0007281 from head to fixes
branch?
It is not usefull to do. There won't be a new release anymore from the
fixes branch.
But what should we do if we can't use trunk because it is not stable
Op Wed, 8 Nov 2006, schreef Martin Schreiber:
On Tuesday 07 November 2006 17.46, Peter Vreman wrote:
Is it possible to backport the resolution of 0007281 from head to fixes
branch?
It is not usefull to do. There won't be a new release anymore from the
fixes branch.
But what
14 matches
Mail list logo
