On Sat, Sep 6, 2014 at 11:42 PM, lee <l...@yun.yagibdah.de> wrote: > [...] > I'd find it hard to believe that there is no reasonable way to check for > new commits that have been made to a remote repo. Git can't be that > bad, can it? (Running 'git diff' for this is not reasonable, and > keeping multiple copies of repos isn't, either.)
git is enough different from cvs and svn that it will seem unreasonable at times. (And it keeps me confused.) Setting up temporary duplicate repositories to experiment on while you're getting used to it is actually a very good idea. But you're right. What you are trying to do doesn't require that. Are you comfortable with the concept that a commit doesn't push the commit to the remote? That's something I tend to forget at times, and then I wonder why my status messages don't make sense. -- Joel Rees Be careful where you see conspiracy. Look first in your own heart, and ask yourself if you are not your own worst enemy. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/caar43iowsoprhetxv5h9pnulwwnem6u6k+nhafyvbgwjjaq...@mail.gmail.com
