---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/112584/#review39585
---
Ship it!
Looks good now. Just fix the trivial things I pointe
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/112584/
---
(Updated Sept. 8, 2013, 4:07 p.m.)
Review request for Calligra and Inge Wa
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/112584/#review39584
---
Looks pretty good, except the disregard for the Calligra coding
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/112584/
---
(Updated Sept. 8, 2013, 2:51 p.m.)
Review request for Calligra and Inge Wa
Hi, Lukas!
The only problem of a rebasing a pushed branch is that you cannot push it
again due to non-fast-forward-merge. If your commits are not destroyed by
the rebase (that could happen with merge commits actually) you can still
push them into repository, but under a different HEAD.
So to do t
DmitryK mentioned some other possibility to preserve history, to create
another branch and merge that new branch.
I would like to preserve the commits as I dropped some code that might be
needed again and squash will destroy history
of the branch.
Dmitry,can you explain the solution with more det
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/111914/
---
(Updated Sept. 8, 2013, 10:33 a.m.)
Review request for Calligra.
Descrip
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/111914/
---
(Updated Sept. 8, 2013, 10:32 a.m.)
Review request for Calligra.
Changes
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/112584/#review39556
---
Hmm, is there a problem? I can't find any diff.
- Inge Wallin
