Thorsten Behrens schrieb:
Hmm - any other way here, without having to pollute a foreign
bugtracker with LibO-specifics? A static list in the wiki maybe?
Hi,
I deal with your concerns, a consequent addition of bug numbers, so that
I can adapt the query link (or the reviewer can add new AOOo
Hi Rainer, *,
On Tue, Feb 14, 2012 at 9:48 AM, Rainer Bielefeld
libreoff...@bielefeldundbuss.de wrote:
Hmm - any other way here, without having to pollute a foreign
bugtracker with LibO-specifics? A static list in the wiki maybe?
I deal with your concerns, a consequent addition of bug
Christian Lohmaier schrieb:
In the wiki you could use the easy-hacks method, i.e. use a query and
add it to the page using the feed tag..
Hi,
great tool, unfortunatly I do not have experince at all. how will it
recognize ÁOoo Issues that have been reviewed by LibO QA?
I would have to add
Hi Rainer, *,
On Tue, Feb 14, 2012 at 12:04 PM, Rainer Bielefeld
libreoff...@bielefeldundbuss.de wrote:
Christian Lohmaier schrieb:
In the wiki you could use the easy-hacks method, i.e. use a query and
add it to the page using the feed tag..
great tool, unfortunatly I do not have experince
Hi @ll !
Why do not use a Metabug like:
https://bugs.freedesktop.org/show_bug.cgi?id=6
There is a: See Also: Add Bug URLs: and comments...
IMHO that would be much easier...
--
Tschüss! | Bye!
Florian Reisinger
LibO 3.5rc3
Windows 7 SP1 64-bit
On Tue, 2012-02-14 at 16:16 +0100, Jan Holesovsky wrote:
Markus has implemented a nice feature that should help keeping the bugs
up to date: whenever you are committing / pushing to git, and you
ooh ! really lovely :-)
Great work Markus !
Michael.
--
On 14.02.2012 19:31, Michael Meeks wrote:
On Tue, 2012-02-14 at 16:16 +0100, Jan Holesovsky wrote:
Markus has implemented a nice feature that should help keeping the bugs
up to date: whenever you are committing / pushing to git, and you
ooh ! really lovely :-)
Great work
hello,
The bug reference has to have fdo#ABCDE form (where ABCDE is the bug
number), and has to be at the first line of the commit (it does not
matter where on that line).
Sorry, one point is for me not clear:
by the first line, do you mean title line or would it works also as
first line of
On Tue, 2012-02-14 at 20:33 +0400, Ivan Timofeev wrote:
Is it possible somehow include the information about a target version?
I guess that -should- be implicit in the branch it is committed to, so
- sounds feasible ;-) at least - the expert eye can see that information
there already.
Hello,
I have been used to see Bugzilla respecting my screen width, for nearby
all bugs Bugzilla line length for the comments matched with my screen
width. Some days ago behavior changed, Page heading and footer still
match perfectly with screen width, but now the text lines of comments
are
On 14/02/12 22:35, Cor Nouws wrote:
Pedro wrote (14-02-12 22:33)
is released and the About box says
LibreOffice 3.5.0rc3
IIRC, this is as usual: after the final RC no new builds are made, so no
strings are updated :-)
This should be fixed ASAP from a marketing point of view. It's
2012/2/14 Pedro pedl...@gmail.com
Olav Dahlum wrote
This should be fixed ASAP from a marketing point of view. It's all about
expectations, so renaming the tarball etc is just not good enough.
Leif did also receive a similar complaint earlier, so this should be
taken very seriously.
12 matches
Mail list logo
