Re: How to check new commit availability without full fetch?
- From
- Leo Razoumov <slonik.az@gmail.com>
- Date
- Jan 11, 2010, 16:22 UTC
- Message-ID
- <ee2a733e1001110822t1b04c1ccg9b6eb5489b69783d@mail.gmail.com>
- In-Reply-To
- <alpine.LFD.2.00.1001102055070.10143@xanadu.home>
On 2010-01-10, Nicolas Pitre <nico@fluxnic.net> 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--