From: Thomas Rast Date: Sun, 12 May 2013 09:41:45 GMT Subject: Re: [PATCH 4/4] fetch: opportunistically update tracking refs Message-ID: <87r4hcedra.fsf@linux-k42r.v.cablecom.net> In-Reply-To: <871u9cftjv.fsf@linux-k42r.v.cablecom.net> Thomas Rast writes: > Jeff King writes: > >> When we run a regular "git fetch" without arguments, we >> update the tracking refs according to the configured >> refspec. However, when we run "git fetch origin master" (or >> "git pull origin master"), we do not look at the configured >> refspecs at all, and just update FETCH_HEAD. >> >> We miss an opportunity to update "refs/remotes/origin/master" >> (or whatever the user has configured). Some users find this >> confusing, because they would want to do further comparisons >> against the old state of the remote master, like: >> >> $ git pull origin master >> $ git log HEAD...origin/master > > I agree with the patch, but I would use a different reasoning. Your > example here is not even correct because the range in the second command > would be empty unless the merge conflicted. Meh, I just read this again and saw that you actually had *three* dots. Serves me right for writing a reply on the phone. So the quoted part is indeed correct. -- Thomas Rast trast@{inf,student}.ethz.ch