Lately, I have been experimenting with using Valgrind in my OPNET Discrete Event Simulations. So far, I've noticed that every time Valgrind runs the runsim executable, the models are recompiled, and I have been using full-stack IP models, so I need to start smaller.
While in the past I've held a pretty high opinion to using mercurial for version control, the majority of version control these days seems to done in git. Here were the commands I found most useful to get productive with git right away. # Clone a repository from an origin, i.e. my github MaskingUtils repository git clone git@github.com:caelumvox/masking-utils.git # Add a file after it's been updated to stage it for commit, or add a new file git add filename # Commit the file to local repo git commit # Push the file to the origin so the rest of the team can see it git push # List all locally tracked branches git branch git branch --list # Get a list of all branches from the remote git branch -r # Create branch locally git branch develop # Push the branch to the origin repository to make sure it is tracked there git push --set-upstream origin develop # Pulls latest from all local branches tracked from origin; won't pull non-tracked branches git pull --all # Fetch the branch ...
Comments
Post a Comment