I think you have it right. Branching and merging every time you switch machines does seem silly.
You can use fetch using --dry-run to see if your *remote*/*branch* pointers would be updated, but that's not really comparing your local to remote. On Sunday, May 17, 2015 at 1:41:00 PM UTC-4, John Bleichert wrote: > > Hello All, > > I have been using git for a while and understand the tooling fairly well. > As the only user of a specific git repo across several machines I simply > push when done on one machine and then fetch when moving to a different > machine. For instance when closing my laptop for the day and moving to my > workstation. > > There seems to be no real way to check the status of my local repo against > the remote (which is the origin master). I only know I need to fetch if I > know personally that I have pushed changes from a different machine. > > I understand that the underlying git principle is that "everything is > local". Is there really no way to compare local to remote? > > Alternatively, should I be branching and merging every time I switch > machines? This seems a strange way to use the tool. > > As I said - hi level question and, otherwise, everything works fine. > > Am I missing something fundamental? > > Thanks, > > John > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
