-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2011-12-05 20:06, Nicolas Montgermont wrote: > Hello Iohannes / list, > > I've worked on a few help files. It was mainly help files that were not > in the Gem format. > I've done that using git. > > You can find them here: > [email protected]:nixhol/Gem.git > the name of the branch is: > help-files > > I've cloned the Gem sourceforge repository, then i've created a branch, > worked on the files, and then i've pushed my modifs on my github > repository. > Is this the good workflow for contributing to Gem using git? or do you > prefer another way?
yes, i think this is the best way to contribute to Gem. i incorporated your fixes and pushed to sourceforge. i'm not yet sure whether it is best to _merge_ your branch into master or to _rebase_ it onto master. for know i prefer a rebase (if possible), but if that makes problems for somebody i could do merges as well. gamsd IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7eLIgACgkQkX2Xpv6ydvQ6NQCeNv395DdyWXIlvGsRUz4ofd04 hPkAniQB10HEeAe9oz0gtLHCsg9nwtTF =dpsr -----END PGP SIGNATURE-----
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ GEM-dev mailing list [email protected] http://lists.puredata.info/listinfo/gem-dev
