Petr Baudis <pasky@xxxxxxx> writes:
> I think that having two commands that by now do essentially the same
> thing, but slightly differently, is rather messy UI. Thus, I'm wondering
> if it would be worthwhile to make rev-list a thin git-log wrapper and
> start phasing it out?
Two answers and a half.
(1) There are a few things git-log does not do but git-rev-list is
designed to do.
(2) They are _already_ thin wrappers to the same core "revision
traversal" engine, and each of them does what it is meant to do well
as specified.
(3) rev-list is an established script interface. You could enhance it if
it does not fit your Porcelain needs, but you cannot break it, let
alone phase it out. What you can contribute is perhaps to document
it better so that casual end users do not accidentally try to use
rev-list as if it is the first class end-user interface and get
confused.
I do not think there is much to be gained by further refactoring of the
implementations between the two.
--
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
