First, a backend that works exactly like git is very different from one that works almost like git. You'll be blamed for other people's problems.
Second, you'll have to have a way to deal with commit history the way git does (arbitrarily, and able to be rewritten at any time)
Otherwise the first push -f or rebase breaks the whole thing.
Reading from and writing to a git backend (that is, making fit a client too) might be the safer option. Sort of like git-p4 in reverse.
First, a backend that works exactly like git is very different from one that works almost like git. You'll be blamed for other people's problems.
Second, you'll have to have a way to deal with commit history the way git does (arbitrarily, and able to be rewritten at any time)
Otherwise the first push -f or rebase breaks the whole thing.
Reading from and writing to a git backend (that is, making fit a client too) might be the safer option. Sort of like git-p4 in reverse.