---
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
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
On 12 April 2012 14:50, Cyrille Berger cber...@cberger.net 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
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 cber...@cberger.net wrote:
I have started to put together a draft of a commit policy:
---
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.
---
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.
---
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
---
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
---
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
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 enter
---
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.
On 12 April 2012 22:25, Jaroslaw Staniek stan...@kde.org 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
---
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.,
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 on
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 document
---
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
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
17 matches
Mail list logo
