From: Michael Haggerty <mhagger@alum.mit.edu>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2017, #02; Mon, 6)
Date: Thu, 9 Feb 2017 17:08:13 +0100 [thread overview]
Message-ID: <2f67fc21-92f9-a03e-1b09-a237af6dbc46@alum.mit.edu> (raw)
In-Reply-To: <xmqqzihzymn3.fsf@gitster.mtv.corp.google.com>
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@alum.mit.edu>
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@alum.mit.edu/
next prev parent reply other threads:[~2017-02-09 16:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 22:34 What's cooking in git.git (Feb 2017, #02; Mon, 6) Junio C Hamano
2017-02-07 0:24 ` SZEDER Gábor
2017-02-07 1:17 ` Jacob Keller
2017-02-07 20:01 ` Junio C Hamano
2017-02-09 0:25 ` Stefan Beller
2017-02-09 1:01 ` Junio C Hamano
2017-02-09 3:46 ` Jeff King
2017-02-09 5:09 ` Junio C Hamano
2017-02-10 21:17 ` Junio C Hamano
2017-02-09 12:29 ` Johannes Schindelin
2017-02-09 17:20 ` Junio C Hamano
2017-02-09 20:37 ` Johannes Schindelin
2017-02-09 22:02 ` Junio C Hamano
2017-02-09 22:32 ` Johannes Schindelin
2017-02-09 16:08 ` Michael Haggerty [this message]
2017-02-09 19:18 ` Junio C Hamano
2017-02-09 19:24 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2f67fc21-92f9-a03e-1b09-a237af6dbc46@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).