From: Junio C Hamano <junkio@cox.net>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Mark Levedahl <mdl123@verizon.net>,
Mark Levedahl <mlevedahl@verizon.net>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: autoCRLF, git status, git-gui, what is the desired behavior?
Date: Sun, 25 Feb 2007 18:45:25 -0800 [thread overview]
Message-ID: <7v649pr60q.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20070226020657.GA1884@spearce.org> (Shawn O. Pearce's message of "Sun, 25 Feb 2007 21:06:57 -0500")
"Shawn O. Pearce" <spearce@spearce.org> writes:
> 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?
next prev parent reply other threads:[~2007-02-26 2:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-25 19:33 autoCRLF, git status, git-gui, what is the desired behavior? Mark Levedahl
2007-02-25 19:54 ` Junio C Hamano
2007-02-25 20:28 ` Junio C Hamano
2007-02-25 21:14 ` Mark Levedahl
2007-02-25 21:22 ` Junio C Hamano
2007-02-25 22:20 ` Mark Levedahl
2007-02-25 23:55 ` Mark Levedahl
2007-02-25 20:51 ` Mark Levedahl
2007-02-26 2:06 ` Shawn O. Pearce
2007-02-26 2:45 ` Junio C Hamano [this message]
2007-02-26 15:54 ` Shawn O. Pearce
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7v649pr60q.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=mdl123@verizon.net \
--cc=mlevedahl@verizon.net \
--cc=spearce@spearce.org \
/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.
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 NNTP newsgroup(s).