-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [EMAIL PROTECTED] wrote: >>For write access i'm not really sure what i should do... > I suggest that you turn it around -- instead of giving developer X write > access > to your repo, you instead arrange for you to have read access to his repo, and > you pull from it regularly. > That's indeed a possibility.. Maybe i could set up a mailinglist for the developers to send and receive patches.. But i'm not entirely sure that i like the feeling that the 'official' repository completely depends on me to receive it's patches. This would mean that there would be no updates to that repo if i'm away for a few weeks.. On the other side... For the devs this wouldn't be a problem because they would receive the patches through the mailinglist. So it would only matter for non-dev people that want to try out the latest code.
How do other projects do this? Greetz, Jeroen - -- <TeRanEX/> --- e-mail: [EMAIL PROTECTED] - jid: [EMAIL PROTECTED] --- blog: http://budts.be/weblog/ - cv: http://budts.be/jeroen/ --- projects: http://lightyear.be - pgp: 0x8B7B774A ___________________________________ GetFirefox.com - rediscover the web -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDRY9HH04wF4t7d0oRAnMZAJ9Q9sNgPcrUNeKEIDzvAs6MvIzr0wCfYm88 9w2GGFdGyCp41OytzKolHfw= =WHZb -----END PGP SIGNATURE----- _______________________________________________ darcs-users mailing list [email protected] http://www.abridgegame.org/mailman/listinfo/darcs-users
