Re: [dev] [scron] simple cron daemon

From: Chris Down <chris_AT_chrisdown.name>
Date: Sun, 6 Jul 2014 13:08:50 +0800

D┼żen writes:
> Why fork scron if you could just provide useful patches to the
> original author?

To expand further on FRIGN's reply, forking with Git is not as
destructive as it would be with, say, CVS or SVN. There are standard
tools that can quite easily integrate the forked upstream back to
mainline if desired, even if a lot of commits have passed since the
initial forking.

For large patch sets, forking and then notifying the mainline
maintainer(s) is a fairly reasonable alternative to sending in a lot of
patches. Both methods provide similar amounts of work to the maintainer
when merging them back into mainline.

Received on Sun Jul 06 2014 - 07:08:50 CEST

This archive was generated by hypermail 2.3.0 : Sun Jul 06 2014 - 07:12:06 CEST