Thanks for your comments. Rearranging them: > This makes me wonder why we don't also change index-pack to write a > similar message to the .promisor. I guess there's potentially too much > information to shove all the refs on the command-line? index-pack already is capable of writing messages to .promisor using the "--promisor" argument. You're right that I'm not using that because I don't want to run into argument length limits. > I am not sure why we want to tie creating the .promisor to creating the > lockfile. I'll keep reading and see if it becomes clear later. Other > than that, the logic here seems clear. [snip] > Apart from using the lockfile name as the base for the .promisor > filename, I'm still not seeing why we need to tie this to the fact that > we're creating a lockfile. Could we instead just unconditionally create > the .promisor when args->from_promisor is set, and then remove the logic > in the previous chunk that adds the "--promisor" flag to the index-pack > call? I'm tying the promisor to the lockfile to avoid overcomplicating things: fetch-pack currently reads filename information from index-pack only when there is a lockfile. (It could do so even when there is no lockfile, but it currently does not.) We need this filename to know what to call the ".promisor" file. And the situation that I'm interested in - when the user fetches with "git fetch" from http or ssh - always uses a lockfile (see fetch_refs_via_pack() in transport.c). So I'm writing additional data in this case, and falling back on the "--promisor" flag otherwise. I'll elaborate in the commit message.
