From: Aghiles <aghilesk@gmail.com>
To: Johannes Gilger <heipei@hackvalue.de>
Cc: git@vger.kernel.org
Subject: Re: git log of remote repositories.
Date: Wed, 14 Apr 2010 15:08:25 -0400 [thread overview]
Message-ID: <x2q3abd05a91004141208x6e154385l8b7ce6488d65f21b@mail.gmail.com> (raw)
In-Reply-To: <slrnhsba0k.h9q.heipei@dualtron.heipei.net>
On Wed, Apr 14, 2010, Johannes Gilger wrote:
> AFAIK no, the operations have to be local.
>
> In order to see if there are any new changes to be pulled you could do
> this: git fetch --dry-run
It seems to me like a major restriction! Especially that I am tracking
a remote branch ... No possibilities to do a diff or a log without fetching?
Very sad. :(
-- aghiles
next prev parent reply other threads:[~2010-04-14 19:08 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
2010-04-14 2:15 ` Dave Olszewski
2010-04-14 11:33 ` Johannes Gilger
2010-04-14 19:08 ` Aghiles [this message]
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=x2q3abd05a91004141208x6e154385l8b7ce6488d65f21b@mail.gmail.com \
--to=aghilesk@gmail.com \
--cc=git@vger.kernel.org \
--cc=heipei@hackvalue.de \
/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).