Andreas Schwab <schwab@xxxxxxxxxxxxxx> wrote: > perryh@xxxxxxxxxxxxxx writes: > > How do I get "git blame" to operate "as of" a particular date in > > the past, without having to manually look up the corresponding > > SHA1 using "git rev-list"? > > You can use any rev-list option, so --until=2011-12-27 should work. That gets rid of the warning message, but it doesn't produce the desired results. Whether specified as $ git blame <file> --until=2011-12-27 or $ git blame --until=2011-12-27 <file> the report still includes commits that are much more recent than 2011-12-27, and it omits material that was deleted since then -- material which _is_ included when specifying the SHA1 of the commit which the --until should have identified. IOW, the --until seems to be silently ignored. I guess this is a bug if rev-list options are supposed to work in "git blame". If they are _not_ supposed to work there, I would claim that the failure to generate an error or warning message (when I've asked for something that's not intended to work) is a bug. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html