On 05/18/2011 11:45 AM, Darren Dale wrote: >> >> I suspect the anomalies have not resulted from forced pushes, but from >> local pulls and merges followed by innocuous pushes. So the key is >> understanding how to ensure one's local branches have the desired >> history before pushing to github. (And making sure one is pushing from >> the correct source to the correct destination. Trying first with >> --dry-run can help.) > > Before pushing, I also recommend inspecting the history graph, either > with "gitk --all" or "git log --oneline --graph --all". I try to > remember to make sure the history graph looks the way I expect it > should before I push anywhere.
QGit is another alternative. Eric ------------------------------------------------------------------------------ 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 _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
