Patrick Steinhardt <ps@xxxxxx> writes: >> > + * Git commands. To do so, we: >> > + * >> > + * - Create an invalid HEAD ref pointing at "refs/heads/.invalid". >> > + * >> > + * - Create the "refs/" directory. >> > + * >> > + * - Set up the ref storage format and repository version as >> > + * required. >> >> "as required" by whom and in what way? >> >> "The code to recognize a repository requires them to be set already, >> but they do not have to be the real value---we just assign random >> valid values for now, let remote helper do its work and then set the >> real values after they are done" would be a plausible interpretation >> of the above. Is that what is going on? > > Partially. While we cannot yet determine the object format, we do know > the ref storage format as it is specified by the caller when invoking > git-clone(1) with the `--ref-format=` switch, not by the remote repo. > In that case, we'd have to set up the ref format accordingly and also > set the repository version to "1". Ah, of course. Unlike the object format, we do not say "the other end uses reftable, so we should do the same" and we do not have to, thanks to some artificial limitations added to the reftable backend not to exceed the expressiveness of the files backend. Thanks.
