Re: git: how to figure out with a script what the last commit on remote repo is without fetching it
On Sun, Sep 21, 2014 at 3:43 AM, lee <lee@yun.yagibdah.de> wrote:
> Joel Rees <joel.rees@gmail.com> writes:
>
>> Well, your experience with git and mine are quite different.
>>
>> On Sat, Sep 20, 2014 at 11:15 PM, lee <lee@yun.yagibdah.de> wrote:
>>> Joel Rees <joel.rees@gmail.com> writes:
>>> [...]
>>
>> Let's clear the conversation, it's too cluttered for me to make sense
>> of it any more.
>>
>> cd to your local copy of the repository you want to do some work in.
>> Try these two commands:
>>
>> git log
>
>
> [~/inst/emacs/emacs-git/emacs] git log
>
> ,----
> | commit f0aeb3ae50be0f96cefa391c8483d8be9f81d9f9
> | Merge: 4dbf5c2 9ce4cf2
> | Author: lee <lee@yun.yagibdah.de>
> | Date: Sun Aug 31 18:47:54 2014 +0200
> |
> | Merge branch 'master' of git://git.savannah.gnu.org/emacs
> |
> | [...]
> `----
>
>
>> git branch --list -ar
>
> ,----
> | [~/inst/emacs/emacs-git/emacs] git branch --list -ar
> | origin/HEAD -> origin/master
> | [...]
> | [~/inst/emacs/emacs-git/emacs]
> `----
>
>> What do they tell you?
>
> That it's been a while since I did a 'git pull'?
Well, that, too.
What do
git status
and
git diff
give you?
Mind you, Linus himself says that git is stupid, and he prefers it
that way. Did you catch the part where git is explained as more of a
backing store than a source code control system? That means when you
use git, you get to do more of the "code management" and "team
management" using external processes and tools.
--
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.
Reply to: