You might want to do a 'fit fetch' and then the diff. This should show you te changes wrt the remote repo but without merging in the changes like a fit pull does.
All the best,
Andy
Sent from my iPhone
On Apr 20, 2012, at 14:34, David A Case <case.biomaps.rutgers.edu> wrote:
> I have re-opened write access at git.ambermd.org. But it's probably good
> to be extra careful for a bit: e.g. type "git diff --stat origin/<branchname>"
> and "git push -=dry-run" before your next push.
>
> Note: as Dan and Dave C. reported earlier on the list: typing "git diff --stat
> origin/master" is not sufficient to see if your master and origin/master are
> the same, since this command will not show you things that have been pushed
> to origin/master by someone else since the last time you did a "git pull".
>
> ...dac
>
>
> _______________________________________________
> AMBER-Developers mailing list
> AMBER-Developers.ambermd.org
> http://lists.ambermd.org/mailman/listinfo/amber-developers
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Fri Apr 20 2012 - 12:00:03 PDT
