Re: What's cooking in git.git (May 2017, #08; Mon, 29)

From: Samuel Lijin <sxlijin@gmail.com>
Date: May 29, 2017, 07:51 UTC
Message-ID: <CAJZjrdXwUiGt9fe=TF2MWq_kdCzWVijB6UqRig+Uf4tzxebV5g@mail.gmail.com>
In-Reply-To: <xmqq1sr889lb.fsf@gitster.mtv.corp.google.com>

On Mon, May 29, 2017 at 2:23 AM, Junio C Hamano <gitster@pobox.com> wrote:

Show 14 quoted lines

> * sl/clean-d-ignored-fix (2017-05-24) 6 commits
>   (merged to 'next' on 2017-05-29 at 837c255ae8)
>  + clean: teach clean -d to preserve ignored paths
>  + dir: expose cmp_name() and check_contains()
>  + dir: hide untracked contents of untracked dirs
>  + dir: recurse into untracked dirs for ignored files
>  + t7061: status --ignored should search untracked dirs
>  + t7300: clean -d should skip dirs with ignored files
>
>  "git clean -d" used to clean directories that has ignored files,
>  even though the command should not lose ignored ones without "-x".
>  This has been corrected.
>
>  Will merge to 'master'.

I noticed the merge commit message (and branch name) don't make mention of the changes to git status --ignored. I forgot to mention it when the last cooking email when out, but was that intended?

I think at the very least, if the branch name isn't updated to reflect that status --ignored is being changed, something like the following should be appended to the merge commit message:

    "git status --ignored" previously did not list ignored files in
untracked directories without -uall, contrary to the documented
behavior of the --ignored flag (that all ignored files would be
listed). This has also been corrected.