"David E. Wheeler" <da...@kineticode.com> writes: > I should think that it'd be pretty damned easy to generate such a > report from a Git repository's log. `git log` is extremely powerful, > and provides a lot of interfaces for hooking things in and sorting. > It's eminently do-able.
Well, it's not like CVS makes it easy ... cvs2cl is about 50K of perl, and is not very speedy or without bugs :-(. So maybe we are setting the goalposts in the wrong place by supposing that the lowest-level git history needs to be exactly what's wanted for human consumption. As long as it can be postprocessed into the form I do want to look at, and someone will volunteer to write that postprocessor, the question doesn't seem like a showstopper. Meanwhile, there seem to have been ten different solutions proposed to the problem of working with multiple branches/checkouts, and I plead confusion. Anyone want to try to sort out the pluses and minuses? regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers