Re: autoCRLF, git status, git-gui, what is the desired behavior?

From: Junio C Hamano <junkio@cox.net>
Date: Feb 26, 2007, 02:45 UTC
Message-ID: <7v649pr60q.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <20070226020657.GA1884@spearce.org>

"Shawn O. Pearce" <spearce@spearce.org> writes:

Show 8 quoted lines

> Hmm.  Probably not.  In pg I used to compare HEAD^{tree} to the
> tree output by git-write-tree and refuse to make the commit if
> they had the same value.  git-gui just blindly assumes that if a
> file is staged for committing then it won't make an empty commit;
> this is also the behavior in git-commit.sh.
>
> Yet in the case of a merge you may want the same tree and not even
> realize it...

git-commit has been raised with all of these logic during its evolution. Is it a possibility to reuse it somehow?