[Kolab-devel] [Patch management (was: Question about horde patches)

Bernhard Reiter bernhard at intevation.de
Tue Dec 4 17:39:22 CET 2007


On Tuesday 04 December 2007 07:22, Gunnar Wrobel wrote:
> In any case that is the reason why it is better if you submit patches
> for upstream code like horde in the bug tracker. I can then try to get
> it in upstream and maintain it within mercurial.
>
> Of course it would be better if the patch management would be done
> within the realm of *.kolab.org. As far as I know Thomas is still
> pushing for mercurial use for the Kolab project.

I do not think that mercurial SCM is a must have to good patch management.
(And pushing for mercurial seemed to have slowed down other important
infrastructure improvements, so it might have been a bad idea at this point
in general.)

-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/devel/attachments/20071204/146a78b8/attachment.sig>


More information about the devel mailing list