Michael Haggerty <mhagger@xxxxxxxxxxxx> writes: > On 02/06/2017 11:34 PM, Junio C Hamano wrote: >> [...] >> -------------------------------------------------- >> [Stalled] >> [...] >> * mh/ref-remove-empty-directory (2017-01-07) 23 commits >> - files_transaction_commit(): clean up empty directories >> - try_remove_empty_parents(): teach to remove parents of reflogs, too >> - try_remove_empty_parents(): don't trash argument contents >> - try_remove_empty_parents(): rename parameter "name" -> "refname" >> - delete_ref_loose(): inline function >> - delete_ref_loose(): derive loose reference path from lock >> - log_ref_write_1(): inline function >> - log_ref_setup(): manage the name of the reflog file internally >> - log_ref_write_1(): don't depend on logfile argument >> - log_ref_setup(): pass the open file descriptor back to the caller >> - log_ref_setup(): improve robustness against races >> - log_ref_setup(): separate code for create vs non-create >> - log_ref_write(): inline function >> - rename_tmp_log(): improve error reporting >> - rename_tmp_log(): use raceproof_create_file() >> - lock_ref_sha1_basic(): use raceproof_create_file() >> - lock_ref_sha1_basic(): inline constant >> - raceproof_create_file(): new function >> - safe_create_leading_directories(): set errno on SCLD_EXISTS >> - safe_create_leading_directories_const(): preserve errno >> - t5505: use "for-each-ref" to test for the non-existence of references >> - refname_is_safe(): correct docstring >> - files_rename_ref(): tidy up whitespace >> >> Deletion of a branch "foo/bar" could remove .git/refs/heads/foo >> once there no longer is any other branch whose name begins with >> "foo/", but we didn't do so so far. Now we do. >> >> Expecting a reroll. >> cf. <5051c78e-51f9-becd-e1a6-9c0b781d6912@xxxxxxxxxxxx> > > I think you missed v4 of this patch series [1], which is the re-roll > that you were waiting for. And I missed that you missed it... > > Michael > > [1] http://public-inbox.org/git/cover.1483719289.git.mhagger@xxxxxxxxxxxx/ Actually it was worse than that. What the above lists *is* v4; I just failed to update "Expecting a reroll" note when I updated the topic with your rerolled patches, and left it there trusting the now-stale note of mine. Sorry, and a HUGE thanks for noticing the mistake.