I keep an eye on the libMesh Network Graph on GitHub (
https://github.com/libMesh/libmesh/network ) and it looks like Roy might be
doing something bad.
It looks like Roy made a branch... and to keep that branch up to do date
he's been pulling from master (generating merge commits in his branch).
Even though there is no development on that branch.
This is typically a pretty bad idea. Your log is going to turn into
nothing but merge-commits... and it looks like you have this long-running
development branch when you really don't.
When updating a branch from master it is really a good idea to use:
git pull --rebase upstream master
So that you aren't generating merge commits _from_ master unnecessarily.
Now - there are times when this might be ok (like you have a long running
development branch with lots of changes and many people are working with
you on it). But in general this type of thing should be avoided.
I'm not sending this to pick on Roy in particular... this is just your
weekly Git public service announcement ;-)
Derek
------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
