On 2010-01-10, Nicolas Pitre [off-list ref] wrote:
You still don't answer my question though. Again, _why_ do you need to
know about remote commit availability without fetching them?
I use git to track almost all my data (code and otherwise) and spread
it between several computers. I end up with several local repos having
the same local branches. It happens once in a while that I fetch into
a given remote/foo from several local foo branches from different
machines and the operation fails. It happens because the commits have
not been yet consistently distributed among the repos. To do the
forensics and figure out who should update whom first I need a quick
and non-destructive way to fetch dry-run.
--Leo--