Hello Philip, Saturday, February 4, 2023, 1:39:31 AM, you wrote: >> PO> As a 'Distributed'-VCS, cloning the repository would be the de-facto >> PO> normal approach, otherwise you have re-invented centralised VCS ;-) >> >> Cloning repository is a heavy operation by downloading everything instead of search a single commit. >> And searching at the remote does not make it a central. PO> It's not local though ;-) PO> Given that there's usually a trusted remote in this scenario (that's why PO> your searching it) I am searching it because it is a fork of many other forks. PO> it does feel very like a 'centralised' VCS, even if PO> formally is isn't stated as such. It feels not. I don't see how this is connected to anything. >> >> PO> Alternatively, you could approach the server (hub/web interface) >> PO> provider to see if they are willing to provide that level of search >> PO> interface. >> >> The GitHub already provides that in the search field. Just input a hash and see what happens. PO> There is still a need to walk the commit graph to discover each commit's PO> tree to do the look-back. There are some catch 22 steps to be done. Calculate a hash from an ordered sourcetree diff is not 22 steps. PO> How do you determine the sourcetree has that starts this process? (have PO> we accidentally created an XY problem?) PO> Obliterating history is hard [1]. PO> -- PO> Philip PO> [1] PO> https://lore.kernel.org/git/5cab1530-f8b6-cef3-7b93-48fad410a160@iee.email/ How this related to the issue?
