On May 22, 2011, at 12:37 PM, Alexander J. Vondrak wrote: > I haven't pushed the changes to my github yet. Is there any etiquette about > handling commits I should know while working on that? For graphviz, I just > used a separate repo in work/ for my personal purposes, then copied the result > into extra/ to push to github, which seems pretty lame. Is it cool to just > commit as much as I want in a branch, or does that clutter the git logs too > much when it's merged later?
Nice work, Alex. Don't worry about the commit logs being too dirty or anything. The best thing would be to just fork github.com/slavapestov/factor/ (or use any old git host) and post here with the fork and branch name when you're ready to commit upstream. -Joe ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Factor-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/factor-talk
