SZEDER Gábor <szeder@xxxxxxxxxx> writes:
> Fortunately, fixing 2) is a no-brainer:
I don't think it is a "no-brainer" to "fix" it, even though it may be so
to hack it around. Having to give "--date=default" to "git log -g" to
cause it to show reflog entries in non-date format sounds like a terrible
UI bug to me. I'd expect
$ git log -g --date=default
to give you the logs in the default date format, overriding log.date, and
perhaps either of these
$ git log -g --no-date
$ git log -g --date=no
$ git log -g --numbered
to countermand log.date and force it to show numbered entries.
I _think_ "git log -g" uses a hacky heuristics to choose between date/number
based on how you give the stating ref. I personally do not like this dwim
very much, but it seems to be stable and established by now, so it may be
a good thing to use here instead:
$ git log -g refs/stash@{0}
$ git log -g refs/stash@{now}
--
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