From: Junio C Hamano Date: Thu, 04 Jan 2024 22:14:50 GMT Subject: Re: Concurrent fetch commands Message-ID: In-Reply-To: <20240104205408.h5wvcissfbat7acw@glandium.org> Mike Hommey writes: > On Thu, Jan 04, 2024 at 01:01:26PM +0100, Stefan Haller wrote: >> On 03.01.24 23:10, Junio C Hamano wrote: >> > Folks who invented "git maintenance" designed their "prefetch" task >> > to perform the best practice, without interfering any foreground >> > fetches by not touching FETCH_HEAD and the remote-tracking branches. >> >> That's good, but it's for a very different purpose than an IDE's >> background fetch. git maintenance's prefetch is just to improve >> performance for the next pull; the point of an IDE's background fetch is >> to show me which of my remote branches have new stuff that I might be >> interested in pulling, without having to fetch myself. So I *want* this >> to be mucking with my remote-tracking branches. > > Use `git remote update`? Hmph, it seems that it does not pass "--no-write-fetch-head" so it would interfere with the foreground "fetch" or "pull" the end user consciously makes, exactly the same way Stefan's demonstration in the first message in the thread, no?