Git development
 help / color / mirror / Atom feed
From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Git repository mesh?
Date: Wed, 25 Nov 2009 12:54:32 +0100	[thread overview]
Message-ID: <vpqy6lues5j.fsf@bauges.imag.fr> (raw)
In-Reply-To: <fcaeb9bf0911250000u395c0153q43c8c7a60ca9b876@mail.gmail.com> (Nguyen Thai Ngoc Duy's message of "Wed\, 25 Nov 2009 15\:00\:28 +0700")

Nguyen Thai Ngoc Duy <pclouds@gmail.com> writes:

> On Wed, Nov 25, 2009 at 2:55 PM, Matthieu Moy
> <Matthieu.Moy@grenoble-inp.fr> wrote:
>> Nguyen Thai Ngoc Duy <pclouds@gmail.com> writes:
>>
>>> 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/

  reply	other threads:[~2009-11-25 11:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-25  4:07 Git repository mesh? Nguyen Thai Ngoc Duy
2009-11-25  7:55 ` Matthieu Moy
2009-11-25  8:00   ` Nguyen Thai Ngoc Duy
2009-11-25 11:54     ` Matthieu Moy [this message]
2009-11-25 12:16       ` Nguyen Thai Ngoc Duy
2009-11-25 13:26         ` Jakub Narebski
2009-11-25 18:23         ` Matthieu Moy
2009-11-25  8:42 ` Sergio
2009-11-25 10:08 ` Alex Riesen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=vpqy6lues5j.fsf@bauges.imag.fr \
    --to=matthieu.moy@grenoble-inp.fr \
    --cc=git@vger.kernel.org \
    --cc=pclouds@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox