This question has been flagged
2 Replies
5307 Views

... I think that would be good to know whenever there are reports about problems resulting from updates (so you can compare the commit ID's and know whether you are running on the same commit or not)

Avatar
Discard
Best Answer

Hi gunnar,

Try using "git hist" in the console to see all your commits. There will appear something like this:

* ab6d116 2014-09-17 | change in README (HEAD, master) [Juan José]
* 2f17612 2014-09-10 | Change index.html (style) [Juan José]
* 166b16e 2014-09-10 | Added css stylesheet [Juan José]
* 8e62b14 2014-09-10 | Added README [Juan José]
* a07f958 2014-08-27 | add index [Juan José]
* 88964bc 2014-08-27 | moved hello.txt to lib [Juan José]

Regards,

Juan José - Ing ADHOC

 

Avatar
Discard
Author

sounds good but is not working for me. I get a "git: 'hist' is not a git command. See 'git --help'." error.

Author

oh yes, and the manpage of git does not show any command like 'git hist' or similar. Seems 'git log' might be something to look at

You have to write "git hist" without the ":". Its really a good command to know your commits, try it.

Author

yes sure. just git hist ... I really get the error posted git: 'hist' is not a git command. See 'git --help' Also there is no manpage for "man git-hist", neither I can find it under "git help -a". Seems we live on a different git-planets.

Author Best Answer

This is my solution for now:

copy (or write down) the "latest commit"-ID from the github site of my remote origin https://github.com/OCA/OCB/ (branch 8.0)

cd /opt/odoo/odoo-server

git log | grep ["latest commit"-ID]

if I don't get any ouput from running that, I know I have not pulled or fetched/merged the "latest commit" yet

Avatar
Discard