On 05 Aug 2011, at 03:33, Alexander Klenin wrote:
> On Fri, Aug 5, 2011 at 02:09, Jonas Maebe wrote:
>> Branching for a major release is most appropriate when trunk is in a settled
>> down/stable state. It's not intended to happen right after a number of major
>> last minute changes have been co
On Fri, Aug 5, 2011 at 19:39, Jonas Maebe wrote:
>> So, TAChart will have to carry numlib fork until 2.6.2 ?
>
> It's always possible. FPC releases are not based on "feature X will certainly
> be in it". We tried that (we were not going to do the next major release
> before the cpstrnew branch w
On 05 Aug 2011, at 10:49, Alexander Klenin wrote:
On Fri, Aug 5, 2011 at 19:39, Jonas Maebe
wrote:
So, TAChart will have to carry numlib fork until 2.6.2 ?
It's always possible. FPC releases are not based on "feature X will
certainly be in it". We tried that (we were not going to do the
That's why we have snapshots. The main purpose of a release is to have
something that is stable and which doesn't break previously working
code (except in known cases documented at
http://wiki.freepascal.org/User_Changes_Trunk ).
Are there published some rules, what breakage is acceptable,
On Thu, August 4, 2011 22:32, Marcus Sackrow wrote:
> Diff (on top of 18076) for new Target: AROS (i386)
> tried to keep the diff as short as possible but its still 750 K,
> so I placed it on my Webpage:
>
> http://www.alb42.de/AROS-Target.diff
>
> Compiler, RTL and Package: arosunits
>
> I hope it
On 05 Aug 2011, at 12:19, LacaK wrote:
That's why we have snapshots. The main purpose of a release is to
have something that is stable and which doesn't break previously
working code (except in known cases documented at http://wiki.freepascal.org/User_Changes_Trunk
).
Are there published s
On 05.08.2011 12:27, Tomas Hajny wrote:
On Thu, August 4, 2011 22:32, Marcus Sackrow wrote:
Diff (on top of 18076) for new Target: AROS (i386)
tried to keep the diff as short as possible but its still 750 K,
so I placed it on my Webpage:
http://www.alb42.de/AROS-Target.diff
Compiler, RTL and P
Hi,
On Fri, 5 Aug 2011, Marcus Sackrow wrote:
> perhaps I didnt choose the name for the define well
> in fact I'm a little bit in trouble here because normaly at amiga
> /xxx/ would be in something like ../xxx/ (in Linux) and so its implemented in
> FExpand atm,
> but the make util (and much oth
Hi,
On Fri, 5 Aug 2011, Karoly Balogh wrote:
> The problem with your example in particular that /System/Development as
> Amiga path is perfectly valid, as it means ../System/Development in POSIX
> path, not System:Development/ Having this in FExpand() affects all apps
> using the RTL on AROS, and
On 5/8/2011 03:05, LacaK wrote:
Luiz Americo Pereira Camara wrote / napísal(a):
On 4/8/2011 09:21, LacaK wrote:
Is this "branching" somehow related to preparation of release some
next version of FPC (2.5.x ? or so) ?
I am asking because, there are waiting some bugs/features which I
would be h
10 matches
Mail list logo
