Thanks, Jason!
I already applied this on all machines on which I use git :)
All the best,
Andy
On Apr 26, 2012, at 8:05 AM, Jason Swails wrote:
> Hello everyone,
>
> This is a quick bit of advice based on some recent experiences with git.
> On many systems, a "git push" will push all of your local branches into a
> remote (specifically the one tracked by your current branch) based on
> matching branch names. Therefore, if you have residual commits in another
> branch, it will (try to) push those as well, which is often undesired
> behavior.
>
> To fix that, run this command (anywhere):
>
> git config --global push.default tracking
>
> This will make it so a "git push" only pushes your current branch to the
> branch that it is tracking. You can also set this behavior on a
> repo-by-repo basis by getting rid of the "--global" flag and running that
> command in a repo.
>
> I have added this advice to the Wiki:
> http://ambermd.org/pmwiki/index.php/Main/Coding
>
> All the best,
> Jason
>
> --
> Jason M. Swails
> Quantum Theory Project,
> University of Florida
> Ph.D. Candidate
> 352-392-4032
> _______________________________________________
> AMBER-Developers mailing list
> AMBER-Developers.ambermd.org
> http://lists.ambermd.org/mailman/listinfo/amber-developers
--
Dr. Andreas W. Goetz
Assistant Project Scientist
San Diego Supercomputer Center
Tel : +1-858-822-4771
Email: agoetz.sdsc.edu
Web : www.awgoetz.de
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Thu Apr 26 2012 - 14:30:03 PDT