Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: >> This commit provides basic utility classes for the reftable library. >> >> Since the reftable library must compile standalone, there may be some overlap >> with git-core utility functions. > > My position on this idea to duplicate functionality in order to somehow > pretend that the reftable code is independent of Git's source code has not > changed. The above may be sufficient between you and Han-Wen, and a few selected others who still remember, but please do not forget that we are collaborating in the open. It would help those who are learning open source interactions by watching from sidelines, if you spelled out what your position is or at least left a pointer to a previous discussion. FWIW, I think it is a mistake to try to make this directory so that it can be lifted out of our code base and used independently, as it has to create unnecessary friction to the code when used here. It is not like other code that we are not their primary intended audience and we simply "borrow" from them (e.g. xdiff/ & sha1dc/). The previous paragraph agrees with my guess of your position, but perhaps you have something else in mind. I dunno. > Be that as it may, the CI build failures impacted my notifications' > signal/noise ratio too much, so here goes (Junio, I would be delighted if > you could apply this on top of your branch): Quite honestly, this close to the first preview release for 2.29, I'd rather drop this round from 'seen' and expect an updated topic, than piling fixup on top of fixups. Thanks.
