On Thursday 12 April 2012 20:05:51 PM Friedrich W. H. Kossebau wrote:
> did I see correctly and there is no OpenDocument format test suite yet?
There are collections of files, but no description of what they should look
like. E.g. a document with a black box on a white background could be checked
Hi
I was thinking that since calligracommon bugs normally fall outside the itches
each of us like to scratch the number of bugs in that component will just
continue to grow
I suggest we organize an online coding sprint where each of us fixes two bugs
from that component.
If we are 20 hackers
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104560/#review12376
---
Do you have a screen shot on how the arrows should look like in
Hello,
On Thursday, April 12, 2012 20:05:51 Friedrich W. H. Kossebau wrote:
> Hi,
>
> did I see correctly and there is no OpenDocument format test suite yet?
> Like there is for SVG, e.g.
> www.w3.org/Graphics/SVG/WG/wiki/Test_Suite_Overview? One that checks the
> rendering or the internal docume
On Thursday, April 12, 2012 14:50:03 Cyrille Berger wrote:
> I have started to put together a draft of a commit policy:
>
> http://community.kde.org/Calligra/Policies/Commits
>
> For now, it is essentially what I said in my emails.
>
> For the git bisect part, maybe we could have some guideline
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104572/#review12371
---
Ship it!
- Jarosław Staniek
On April 12, 2012, 9:35 p.m., Ad
On 12 April 2012 22:25, Jaroslaw Staniek wrote:
> BTW, is there somewhere documented recommended post-review script and
> recipe specific for calligra development?
>
> I have this:
Updated (don't read if you have your own solution ready):
#!/bin/bash
# post-review-master
# git remote add calligr
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104572/
---
Review request for Calligra, Jarosław Staniek and Dimitrios Tanis.
Descrip
BTW, is there somewhere documented recommended post-review script and
recipe specific for calligra development?
I have this:
#!/bin/bash
# first run: git remote add calligra git://anongit.kde.org/calligra
if [ -z "$1" ] ; then echo "enter testing-done"; exit 1; fi
if [ -z "$2" ] ; then echo "ent
Hi,
did I see correctly and there is no OpenDocument format test suite yet? Like
there is for SVG, e.g. www.w3.org/Graphics/SVG/WG/wiki/Test_Suite_Overview?
One that checks the rendering or the internal document model or the
functionality?
All I found are checkers for the file format produced,
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104560/
---
Review request for Calligra.
Description
---
LibreOffice 3.5 has some
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104556/#review12360
---
This review has been submitted with commit
df9a20b4747e5126adb
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104556/#review12359
---
Ship it!
Looks good to me! Thanks!
- Boudewijn Rempt
On Apr
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104556/
---
Review request for Calligra.
Description
---
Currently in Krita's lay
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104556/
---
(Updated April 12, 2012, 2:21 p.m.)
Review request for Calligra.
Descrip
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104556/
---
(Updated April 12, 2012, 2:21 p.m.)
Review request for Calligra.
Descrip
On Thursday 12 April 2012 Apr, Friedrich W. H. Kossebau wrote:
> Am Donnerstag, 12. April 2012, 15:03:43 schrieb Jaroslaw Staniek:
> > On 12 April 2012 14:50, Cyrille Berger wrote:
> > > I have started to put together a draft of a commit policy:
> > >
> > > http://community.kde.org/Calligra/Polic
Am Donnerstag, 12. April 2012, 15:03:43 schrieb Jaroslaw Staniek:
> On 12 April 2012 14:50, Cyrille Berger wrote:
> > I have started to put together a draft of a commit policy:
> >
> > http://community.kde.org/Calligra/Policies/Commits
> >
> > For now, it is essentially what I said in my emails.
On 12 April 2012 14:50, Cyrille Berger wrote:
> I have started to put together a draft of a commit policy:
>
> http://community.kde.org/Calligra/Policies/Commits
>
> For now, it is essentially what I said in my emails.
>
> For the git bisect part, maybe we could have some guideline on what to
> co
I have started to put together a draft of a commit policy:
http://community.kde.org/Calligra/Policies/Commits
For now, it is essentially what I said in my emails.
For the git bisect part, maybe we could have some guideline on what to
commit in branch,
could be useful for beginners as well.
As f
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104553/#review12355
---
This review has been submitted with commit
ab76fda56b1ee6a9ca1
On Thursday, April 12, 2012 08:54:22 Boudewijn Rempt wrote:
> On Wednesday 11 April 2012 Apr, Cyrille Berger Skott wrote:
> > Hi,
> >
> > For me this is how it should be: commits in master are restricted to:
> >
> > * single commit bug fixes
> > * merge from feature branches (or single commit fea
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/104553/#review12353
---
Ship it!
Not much to discuss here. This is a pure bugfix, not
23 matches
Mail list logo
