Re: Git repository mesh?

Nguyen Thai Ngoc Duy [off-list ref] writes:

On Wed, Nov 25, 2009 at 2:55 PM, Matthieu Moy
[off-list ref] wrote:

quoted

Nguyen Thai Ngoc Duy [off-list ref] writes:

quoted

Never used Mercurial but the idea of "git in" and "git out" to see how
many commits ahead/behind would be nice.

In Git, you'd run "git fetch" to get everything locally, and then

git log ..origin/master => what origin/master has that you don't
git log origin/master.. => what you have that origin/master doesn't

(and you can define aliases for that)

But I have many origins (any repository could be origin). "git status"
also have this kind of information, but only for "origin".

Then, fetch from all of them and:

  git log ^HEAD repo1/master repo2/master repo3/master

--
Matthieu Moy
http://www-verimag.imag.fr/~moy/

On 11/25/09, Matthieu Moy [off-list ref] wrote:

Then, fetch from all of them and:

  git log ^HEAD repo1/master repo2/master repo3/master

Very nice. Thanks I did not know about "^HEAD". Now I need to think of
how to avoid typing all "repo*/master" stuff..
-- 
Duy

Nguyen Thai Ngoc Duy [off-list ref] writes:

On 11/25/09, Matthieu Moy [off-list ref] wrote:

quoted

Then, fetch from all of them and:

  git log ^HEAD repo1/master repo2/master repo3/master

Very nice. Thanks I did not know about "^HEAD". Now I need to think of
how to avoid typing all "repo*/master" stuff..

Hmmm... shouldn't 'repo1' expand to 'repo1/HEAD', which is 'repo1/master'?
I mean shouldn't simply

  git log ^HEAD repo1 repo2 repo3

work?

Also, git aliases (so you would be able to just say "git in").

-- 
Jakub Narebski
Poland