From: Robin Rosenberg <robin.rosenberg@dewire.com>
To: SLONIK.AZ@gmail.com
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: How to check new commit availability without full fetch?
Date: Mon, 11 Jan 2010 08:31:28 +0100 [thread overview]
Message-ID: <201001110831.28278.robin.rosenberg@dewire.com> (raw)
In-Reply-To: <ee2a733e1001100312j786108fct1b4c8abd0acc5afc@mail.gmail.com>
söndagen den 10 januari 2010 12.12.09 skrev Leo Razoumov:
> Hi List,
> I am trying to find a way to check availability of new commits
> *before* doing fetch or pull. Unfortunately, neither fetch nor pull
> take "--dry-run" option (unlike push)
Fetch has --dry-run. It's a fairly new option. The drawback is that it
still does the fetch, but it does not update the refs. If you re.run it
again it'll be quicker.
A faster option is to use ls-remote, but you'll have to parse the data
yourself and compare with your remote refs to see what refs has changed,
and that will not tell you /what/ the changes are.
-- robin
next prev parent reply other threads:[~2010-01-11 8:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-10 11:12 How to check new commit availability without full fetch? Leo Razoumov
2010-01-10 20:13 ` Nicolas Pitre
2010-01-10 20:38 ` Junio C Hamano
2010-01-10 21:05 ` Nicolas Pitre
2010-01-11 1:36 ` Leo Razoumov
2010-01-11 1:57 ` Tay Ray Chuan
2010-01-11 2:08 ` Junio C Hamano
2010-01-11 5:29 ` Michael Witten
2010-01-11 7:12 ` Junio C Hamano
2010-01-11 2:01 ` Nicolas Pitre
2010-01-11 16:22 ` Leo Razoumov
2010-01-11 17:04 ` Nicolas Pitre
2010-01-11 17:35 ` Leo Razoumov
2010-01-11 5:38 ` Dmitry Potapov
2010-01-11 7:31 ` Robin Rosenberg [this message]
2010-01-11 8:09 ` Junio C Hamano
2010-01-11 17:59 ` Nicolas Pitre
2010-01-11 19:20 ` Junio C Hamano
2010-01-11 20:52 ` Nicolas Pitre
2010-01-11 20:06 ` Andreas Schwab
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=201001110831.28278.robin.rosenberg@dewire.com \
--to=robin.rosenberg@dewire.com \
--cc=SLONIK.AZ@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).