On Tue, 10 Aug 2010 15:32:41 +0200 Alessio Caiazza <[email protected]> wrote:
> A good idea may be switching to mercurial (as Scintilla did) in order > to facilitate fork and patch queue development, being able to merge > it back when they are ready. > > IMHO http://bitbucket.org may be a good candidate, even better that > sourceforge for repos 'cause, like on github, they allow an easy > management for fork and patch queue. Using a DVCS was already under discussion with a few pros for using git. Maybe you can search a bit inside archive of this list. There has been a huge number of mails around start of June. Beside of the advantages/disadvantages mentioned there I don't see that this will be able to solve the issue, that some of the 'core'devs needs to review a patch before merging it into official trunk. Cheers, Frank -- http://frank.uvena.de/en/
pgpM32JTnrK9t.pgp
Description: PGP signature
_______________________________________________ Geany-devel mailing list [email protected] http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
