Continuing to have relays would not be successful. I'm specifically referring to the day when there is a decentralized backend over which you can use git. I don't know what's not getting across about that, my words seem pretty clear. This means p2p structure, not relays. And it doesn't mean "git is decentralized," it means a single git that is decentralized individually rather than simply relying on decentralized concepts.
Maybe we have a different understanding of "Git"? If so, sorry. My understanding: Git does not have and does not need a backend. In the user's repository you have "remote" connections from which you can pull/push. Git supports various transport protocols for this and as a user I can add as many as I want - all are equal (a github remote is no different to any other remote) Now there are no answers on how to find those remotes and there is no public definition of which clone is the "best" or "newest" (but this is also subjective) And there is no way to communicate proposed changes, etc. Did you look into stuff like https://radicle.xyz/ ?
I do not know much about Radicle but it fits with what I'm talking about. My explanation here comes without ever using git, so bear with me. When you use the command line to command git to interact with some remote storage, you're calling on software programmed to look for a centralized server you point it at, like Microsoft servers in github's case. In my world, when you call on git in your command line to read or write data remotely, your "git" command calls on software programmed to connect to a p2p network like Radicle you just mentioned. Radicle seems like it might be a "decentralized backend" I'm talking about.