Junio C Hamano <gitster@xxxxxxxxx> writes: > Domagoj Stolfa <domagoj.stolfa@xxxxxxxxx> writes: > >> For example, saying: >> >> $ git blame time.h --since=2017 >> ^e19f2a27ed8 (Domagoj Stolfa 2017-03-12 20:43:01 +0100 33) #ifndef _SYS_TIME_H_ >> >> $ git blame time.h --since=2016 >> ^21613a57af9 (bz 2016-03-13 21:26:18 +0000 33) #ifndef _SYS_TIME_H_ >> >> $ git blame time.h --since=2015 >> ^48507f436f0 (mav 2015-03-13 21:01:25 +0000 33) #ifndef _SYS_TIME_H_ >> >> and so on, with different hashes. > > The output lines "^deadbeef" does *NOT* mean that commit deadbeef > changed the revision. It just is telling you that the hisory was > dug down to that revision and it was found that since that revision > there is no change (and you told the command not to bother looking > beyond that time range, so we do not know what happened before that > time). > ... > So it is entirely sane if you saw three boundary commits named with > three different time ranges. Side note. If the displaying of the boundary commit object names are distracting, the user can always use the -b option to blank them out.