Re: How to check new commit availability without full fetch?

From: Junio C Hamano <gitster@pobox.com>
Date: Jan 11, 2010, 08:09 UTC
Message-ID: <7vljg5ukol.fsf@alter.siamese.dyndns.org>
In-Reply-To: <201001110831.28278.robin.rosenberg@dewire.com>

Robin Rosenberg <robin.rosenberg@dewire.com> writes:

Show 9 quoted lines

> 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.

Doesn't that worry us if it really is quicker?

If --dry-run doesn't update the refs, why do the objects that were transferred by them not get asked the next time? There must be a bug somewhere, but it is getting late already, so I'll leave it to experts in the transfer area to figure it out...