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.
pgpNmawFm8FF5.pgp
Description: PGP signature
