On Thu, Aug 9, 2018 at 10:05 AM, Junio C Hamano <gits...@pobox.com> wrote: > Hmm, it is clever to auto-start the pack-objects (and notice there > wasn't anything needing to pack). Two things that are worth noting > are: > > - The code takes advantage of the fact that cmd.in being left as -1 > is a sign that start_command() was never called (well, it could > be that it was called but failed to open pipe---but then we would > have died inside write_oid(), so we can ignore taht case). This > is not relying on its implementation detail---cmd.in would be > replaced by a real fd to the pipe if start_command() was called. > > - We know that pack-objects reads all its standard input through to > the EOF before emitting a single byte to its standard output, and > that is why we can use bidi pipe and not worry about deadlocking > caused by not reading from cmd.out at all (before closing cmd.in, > that is). > > So I kind of like the cleverness of the design of this code.
Thanks for checking this. > For now, as we do not know what is the appropriate thing to leave in > the file, empty is fine, but perhaps in the future we may want to > carry forward the info from the existing .promisor file? What does > it initially contain? Transport invoked with from_promisor bit > seems to call index-pack with "--promisor" option with no argument, > so this is probably in line with that. Do we in the future need to > teach "--promisor" option to pack-objects we invoke here, which will > be passed to the index-pack it internally performs, so that we do > not have to do this by hand here? There might be more than one .promisor file that we are repacking, so we would also have to deal with the order. It might be better to document that the contents of .promisor files are lost upon repack. > In any case, don't we need to update the doc for the "--promisor" > option of "index-pack"? The same comment for the new options added > in the same topic, e.g. "--from-promisor" and "--no-dependents" > options added to "fetch-pack". It seems that the topic that ended > at 0c16cd499d was done rather hastily and under-documented? Yes, you're right - I'll make a patch documenting these. >> @@ -440,6 +513,8 @@ int cmd_repack(int argc, const char **argv, const char >> *prefix) >> >> /* End of pack replacement. */ >> >> + reprepare_packed_git(the_repository); >> + > > I do not think this call hurts, but why does this become suddenly > necessary with _this_ patch? Is it an unrelated bugfix? Hmm...I thought I mentioned somewhere that we need reprepare_packed_git now because for_each_packed_object calls prepare_packed_git, but apparently I didn't. I would add the following to the commit message (if you'd rather not do it yourself, let me know and I'll send a v3 with the new commit message): Because for_each_packed_object() calls prepare_packed_git(), a call to reprepare_packed_git() now has to be inserted after all the packfile manipulation - if not, old information about packed objects would remain in the_repository->objects->packed_git.
