Re: What's cooking in git.git (Jun 2016, #04; Tue, 14)
From: Duy Nguyen <hidden>
Date: 2016-06-16 06:55:53
On Wed, Jun 15, 2016 at 5:08 AM, Junio C Hamano [off-list ref] wrote:
* nd/i-t-a-commitable (2016-06-06) 3 commits - commit: don't count i-t-a entries when checking if the new commit is empty - Resurrect "diff-lib.c: adjust position of i-t-a entries in diff" - diff.h: extend "flags" field to 64 bits because we're out of bits "rm .git/index && git add -N * && git commit" allows you to create an empty commit without --allow-empty; attempt to forbid it. Breaks many tests by completely butchering "git commit", it seems.
Not surprising. I did run some basic tests, but not the test suite. It was more an excuse to bring up the topic again. Please drop it. I will probably resend (with more or less the same idea, since you haven't given a loud and clear "NO").
* nd/worktree-cleanup-post-head-protection (2016-05-24) 6 commits
- worktree: simplify prefixing paths
- worktree: avoid 0{40}, too many zeroes, hard to read
- worktree.c: use is_dot_or_dotdot()
- git-worktree.txt: keep subcommand listing in alphabetical order
- worktree.c: rewrite mark_current_worktree() to avoid strbuf
- completion: support git-worktree
(this branch is used by nd/worktree-lock.)
Further preparatory clean-up for "worktree" feature.
Expecting a reroll.
($gmane/294136, etc.)Hmm.. I think what's in 'pu' (which is v2, $gmane/295260) is ok now. -- Duy