On Tue, Dec 19, 2017 at 11:22 AM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > I had to squash in the following to make 'pu' pass under > gettext-poison build. Is this ready for 'next' otherwise? I saw that in pu, thanks for squashing. I should have spoken up earlier confirming it. > With the "log --find-object" thing, it may be that this no longer is > needed, but then again we haven't done anything with the other > Jonathan's idea to unify the --find-object thing into the --pickaxe > framework. I'll look into that after I finish looking at a submodule related bug. > It seems that we tend to open and then abandon new interests without > seeing them through completion, leaving too many loose ends untied. > This has to stop. I'll try to find my balance again. When working on too few topics at the same time, sometimes I get stalled waiting for the mailing list (or internal reviewers) to respond, so I start many topics, which then overwhelm me after a while once reviews catch up. In this specific case it was not clear what the best way is, i.e. the interest was rather broad: "Hey I have this blob sha1, how do I get more information?", which can be solved in many different ways, so I tried some of them. (Another alternative just now considered: I could have wrapped that script from stackoverflow into a new command and called it a day, though that has very poor benefits for the rest of ecosystem, an addition to an established powerful command gives more benefits IMHO) Thanks, Stefan
