On Thu, Feb 21, 2013 at 5:05 AM, Stefan Fuhrmann
wrote:
>> BTW, how are you managing your branch? I tried merging it back to
>> trunk to get an idea on the diff and there were a lot of text and tree
>> conflicts. I thought I had seen you doing synch merges from trunk in
>> the past so I assumed
On Thu, Feb 21, 2013 at 12:06 PM, Johan Corveleyn wrote:
> On Thu, Feb 21, 2013 at 11:05 AM, Stefan Fuhrmann
> wrote:
> > On Mon, Feb 18, 2013 at 5:54 PM, Mark Phippard
> wrote:
> >> On Sat, Feb 16, 2013 at 4:30 PM, Stefan Fuhrmann
> >> wrote:
> ...
> >> > Quite a number of reasons:
> >> >
> >
On 21.02.2013 12:06, Johan Corveleyn wrote:
> On Thu, Feb 21, 2013 at 11:05 AM, Stefan Fuhrmann
> wrote:
>> On Mon, Feb 18, 2013 at 5:54 PM, Mark Phippard wrote:
>>> On Sat, Feb 16, 2013 at 4:30 PM, Stefan Fuhrmann
>>> wrote:
> ...
Quite a number of reasons:
* easy setup
* mi
On Thu, Feb 21, 2013 at 11:05 AM, Stefan Fuhrmann
wrote:
> On Mon, Feb 18, 2013 at 5:54 PM, Mark Phippard wrote:
>> On Sat, Feb 16, 2013 at 4:30 PM, Stefan Fuhrmann
>> wrote:
...
>> > Quite a number of reasons:
>> >
>> > * easy setup
>> > * minimal overhead (I want to get as close to measuring p
On Mon, Feb 18, 2013 at 1:46 PM, Daniel Shahaf wrote:
> Stefan Fuhrmann wrote on Sat, Feb 16, 2013 at 10:52:21 +0100:
> > Hey all,
> >
> > Just to give you an update on what is going on that branch,
> > here a few facts and numbers. Bottom line is that there is
> > still a lot to do but the basi
On Thu, Feb 21, 2013 at 11:05:56AM +0100, Stefan Fuhrmann wrote:
> On Mon, Feb 18, 2013 at 5:54 PM, Mark Phippard wrote:
> > BTW, how are you managing your branch? I tried merging it back to
> > trunk to get an idea on the diff and there were a lot of text and tree
> > conflicts. I thought I had
On Mon, Feb 18, 2013 at 5:54 PM, Mark Phippard wrote:
> On Sat, Feb 16, 2013 at 4:30 PM, Stefan Fuhrmann
> wrote:
> > On Sat, Feb 16, 2013 at 5:47 PM, Mark Phippard
> wrote:
> >>
> >> On Sat, Feb 16, 2013 at 4:52 AM, Stefan Fuhrmann
> >> wrote:
> >> > Hey all,
> >> >
> >> > Just to give you an
On Sat, Feb 16, 2013 at 4:30 PM, Stefan Fuhrmann
wrote:
> On Sat, Feb 16, 2013 at 5:47 PM, Mark Phippard wrote:
>>
>> On Sat, Feb 16, 2013 at 4:52 AM, Stefan Fuhrmann
>> wrote:
>> > Hey all,
>> >
>> > Just to give you an update on what is going on that branch,
>> > here a few facts and numbers.
Stefan Fuhrmann wrote on Sat, Feb 16, 2013 at 10:52:21 +0100:
> Hey all,
>
> Just to give you an update on what is going on that branch,
> here a few facts and numbers. Bottom line is that there is
> still a lot to do but the basic assumptions proved correct and
> significant benefits can already
On 16.02.2013 22:30, Stefan Fuhrmann wrote:
> '--enable-optimize' is new in 1.8. It should probably be documented
> somewhere but I'm not sure how safe it is to *recommend* it to
> packagers. The optimizations are quite aggressive and might break
> unclean code.
It's about as documented as anythin
On Sat, Feb 16, 2013 at 5:47 PM, Mark Phippard wrote:
> On Sat, Feb 16, 2013 at 4:52 AM, Stefan Fuhrmann
> wrote:
> > Hey all,
> >
> > Just to give you an update on what is going on that branch,
> > here a few facts and numbers. Bottom line is that there is
> > still a lot to do but the basic a
On Sat, Feb 16, 2013 at 4:52 AM, Stefan Fuhrmann
wrote:
> Hey all,
>
> Just to give you an update on what is going on that branch,
> here a few facts and numbers. Bottom line is that there is
> still a lot to do but the basic assumptions proved correct and
> significant benefits can already be de
12 matches
Mail list logo
