Roman, David
Thank you both! Roman's steps make perfect sense, although I was scratching
my head about the "b3a49f990273c9fa6e2b90245c271a14b38280f0" ID, before I
realized it was the commit ID for the patcth to 3.6 and that the cgit
interface allows a toggle between Master and 3.6
Anyhow, turn
On Wed, Oct 24, 2012 at 1:48 PM, Petr Mladek wrote:
> On Tue, 2012-10-23 at 20:24 +0200, Norbert Thiebaud wrote:
>> On Tue, Oct 23, 2012 at 5:25 PM, Petr Mladek wrote:
>> > Hi,
>> >
>> > there have been created the libreoffice-3.6.3.2 tag (aka rc2)[*]. The
>> > corresponding official builds will
On Tue, 2012-10-23 at 20:24 +0200, Norbert Thiebaud wrote:
> On Tue, Oct 23, 2012 at 5:25 PM, Petr Mladek wrote:
> > Hi,
> >
> > there have been created the libreoffice-3.6.3.2 tag (aka rc2)[*]. The
> > corresponding official builds will be available within next few days.
> > It will be used as fi
Le 23/10/2012 19:03, Joel Madero a écrit :
Hi Joel,
> I just wanted to confirm that just because a macro was made in Excel
> doesn't mean it'll work in LibO right? And if a user is reporting a bug
> against an excel macro, the correct path would be tomark as INVALID?
> NOTOURBUG?
My understa
ol klaus-jürgen weghorn wrote
> my 3.6.2.1 is "up to date". Shouldn't be so.
My 3.5.7.1 install reports "LibreOffice 3.5 is up to date."
Shouldn't be so.
--
View this message in context:
http://nabble.documentfoundation.org/Libreoffice-qa-Online-update-testing-tp4001812p4015112.html
Sent from
Hi V Stuart Foote,
Am 23.10.12 20:24, schrieb V Stuart Foote:
The commit for this issue was pushed down to the 3.6 tree, but is there a way
to determine if a specific TinderBox has refreshed and is using a particular
source?
I used Fridrich Strba's TB - 9 Voreppe 2012-10-22 23.52.55 time stampe
