From: "Shawn O. Pearce" <spearce@spearce.org>
To: Aghiles <aghilesk@gmail.com>
Cc: git list <git@vger.kernel.org>
Subject: Re: git log of remote repositories.
Date: Tue, 13 Apr 2010 16:27:47 -0700 [thread overview]
Message-ID: <20100413232747.GD17484@spearce.org> (raw)
In-Reply-To: <u2n3abd05a91004131625k500e79bbsc8ffa6455a85332d@mail.gmail.com>
Aghiles <aghilesk@gmail.com> wrote:
> I have a local branch that is a tracking a remote branch. I want to see
> what are the modifications upstream, _before_ I pull. I tried
> 'git log origin' but that's only the point from where I pulled last.
>
> Is there a way to do that?
git fetch
git log ..origin
--
Shawn.
next prev parent reply other threads:[~2010-04-13 23:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 23:25 git log of remote repositories Aghiles
2010-04-13 23:27 ` Shawn O. Pearce [this message]
2010-04-14 2:15 ` Dave Olszewski
2010-04-14 11:33 ` Johannes Gilger
2010-04-14 19:08 ` Aghiles
2010-04-14 19:43 ` Tomas Carnecky
2010-04-14 19:45 ` Johannes Gilger
2010-04-14 20:05 ` Aghiles
2010-04-14 20:11 ` Sverre Rabbelier
2010-04-14 20:18 ` Aghiles
2010-04-14 20:25 ` Sverre Rabbelier
2010-04-14 20:39 ` Johannes Gilger
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=20100413232747.GD17484@spearce.org \
--to=spearce@spearce.org \
--cc=aghilesk@gmail.com \
--cc=git@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).