Han-Wen Nienhuys <hanwen@xxxxxxxxxx> writes: > On Fri, Jul 17, 2020 at 12:10 AM Junio C Hamano <gitster@xxxxxxxxx> wrote: >> I reviewed some codepaths that deal with FETCH_HEAD recently. >> >> As the file is quite different from all the other pseudo references >> in that it needs to store more than one object name and in that each >> ref in it needs more than just the object name, I doubt that it >> makes much sense to enhance the refs API so that its requirements >> can be covered. > > I agree. Do we ever pretend that FETCH_HEAD is a ref today? "git rev-parse FETCH_HEAD", "git show FETCH_HEAD" etc. all should keep working, so in that sense, it is treated as a ref. It does not protect the history leading to the objects listed in it from being collected, though. "git merge FETCH_HEAD" is an interesting case---I haven't thought it through. Jung fubhyq unccra nsgre "tvg chyy bevtva sbb one" nggrzcgf gb teno gjb oenapurf naq znxr na bpgbchf zretr vagb gur oenapu pheeragyl purpxrq bhg, naq gura "tvg erfrg --uneq && tvg zretr SRGPU_URNQ" vf tvira?
