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

List:       kde-edu-devel
Subject:    Re: [kde-edu-devel] Kalzium: rewrite
From:       Dominique Devriese <dominique.devriese () student ! kuleuven ! ac ! be>
Date:       2004-01-28 11:13:26
Message-ID: 87d69472cp.fsf () student ! kuleuven ! ac ! be
[Download RAW message or body]

Carsten Niehaus writes:

> Hi I have a question: I am currently rewriting Kalzium. I am not
> sure when it will be done, sure not in the next 3 month. Perhaps not
> even in the next 6... This means I can't garantee a working "new"
> Kalzium for KDE 3.3/4.0. The question is: Should I work in a branch
> and merge it with HEAD in case I make it in time or should I do the
> opposite: work in HEAD and put it in a branch in case I don't make
> it (and restore the HEAD to the status of KDE 3.2).

A branch seems most logical to me.  That's at least what I did for the
Kig refactorings in the past.

cheers
domi
_______________________________________________
kde-edu-devel mailing list
kde-edu-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-edu-devel
[prev in list] [next in list] [prev in thread] [next in thread]