[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Re: Change tracker and commit problem
From:       Thomas Zander <zander () kde ! org>
Date:       2008-11-24 23:13:57
Message-ID: 200811250013.57473.zander () kde ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Monday 24. November 2008 23:04:50 Pierre Stirnweiss wrote:
> first I wanted to commit the changes to the branch work/koffice_trk but
> somehow it was committed to trunk. I have to say that I do not know what
> happened or what has gone wrong. So if the powers that be deem necessary
> to uncommit, please do.

Yes, I'm afraid that with the 2.0 release coming up changes this big, even 
if commented out, should go to a branch until trunk is open for commits 
again.

> I would still rather do it on the trunk because keeping a separate branch
> up to date is a real pain.

I suggest using git-svn and use a git branch then while merging the changes 
from trunk ever week or so.
This makes it a lot easier to keep the feature up-to-date.

Naturally its still not free; bugfixes in the code you also changed will 
have to manually be merged. There is no way around that, though.

> Now, on the changetracker itself, which I wanted to get your approval
> first before committing to trunk.

I have not read the patch; I do think its *very* interresting for KOffice 
and I would love to have this feature in 2.1.  I will have little time to 
work on reviewing / cooperation before 2.0 is out, though.   Getting a 
stable 2.0 is very high on my already waaay to long TODO list.
Maybe you can help a little on that part? Getting 2.0 stable since you seem 
to already be confident with the code :)

Thanks for your time so far!!

Rock on.
-- 
Thomas Zander

["signature.asc" (application/pgp-signature)]

_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel


[prev in list] [next in list] [prev in thread] [next in thread]