On Mon, 2014-04-28 at 08:45 +0200, Daniel Pocock wrote:
> Even if there are no other fixes you plan to backport, could you
> consider making a 3.4.5 tag just with this fix?
Hi,
right, I understand the Long Term Support "models" and so on, but it's a
distribution decision. I'm not a fan of
On 28/04/14 07:53, Milan Crha wrote:
> On Sun, 2014-04-27 at 22:03 +0200, Daniel Pocock wrote:
>> Please find the revised version enclosed - I believe this is good for
>> the 3.4 branch in upstream evolution-data-server too:
> Hi,
> I'm sorry, but 3.4 is dead for upstream currently, we are mo
On Sun, 2014-04-27 at 22:03 +0200, Daniel Pocock wrote:
> Please find the revised version enclosed - I believe this is good for
> the 3.4 branch in upstream evolution-data-server too:
Hi,
I'm sorry, but 3.4 is dead for upstream currently, we are more than
3 years ahead from it right now.
On 26/04/14 12:57, Andreas Henriksson wrote:
> Hello Daniel!
>
> On Sat, Apr 26, 2014 at 12:34:08PM +0200, Daniel Pocock wrote:
>> Hi Andreas,
>>
>> Thanks for the feedback about this
>>
>> Can you just clarify about backporting the fix - do you mean backporting
>> the whole version from testing
Hello Daniel!
On Sat, Apr 26, 2014 at 12:34:08PM +0200, Daniel Pocock wrote:
> Hi Andreas,
>
> Thanks for the feedback about this
>
> Can you just clarify about backporting the fix - do you mean backporting
> the whole version from testing to wheezy-backports or just copying the
> individual pat
Hi Andreas,
Thanks for the feedback about this
Can you just clarify about backporting the fix - do you mean backporting
the whole version from testing to wheezy-backports or just copying the
individual patch into a rebuild of the version currently in stable?
Regards,
Daniel
--
To UNSUBSCR
6 matches
Mail list logo
