If you're looking for a git/github workflow I can't recommend the following post enough:
http://blog.mhartl.com/2008/10/14/setting-up-your-git-repositories-for-open-source-projects-at-github/ I use something similar to (barely) contribute to compojure. There isn't anything like his 'edge' branch in compojure so it's a bit simpler. I also branch for each fix or feature (he just creates a single personal branch). It might seem complicated, but it ends up being very clean and more closely matches the command line experience imho (origin is the project, not your github fork). Some things I'd recommend are never ever work on master (should always fast forward), always branch for a feature or fix, and rebase that branch before pushing it to github. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
