From: Junio C Hamano <junkio@cox.net>
To: Petr Baudis <pasky@suse.cz>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Fix bad usage of mkpath in builtin-branch.sh
Date: Wed, 25 Oct 2006 15:51:32 -0700 [thread overview]
Message-ID: <7v3b9cko0b.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20061025224313.GM20017@pasky.or.cz> (Petr Baudis's message of "Thu, 26 Oct 2006 00:43:13 +0200")
Petr Baudis <pasky@suse.cz> writes:
>> +
>> +test "$ret" = 0 && git-diff-tree --summary --root --no-commit-id HEAD
>> +
>> exit "$ret"
>
> Yes, this might be a good idea, although after the commit is perhaps too
> late.
Before the commit I thought we have git-status output in the
commit log buffer.
Ah,...
We had that old issue of "'M foo' cannot tell content or mode
changes (or both)", and people suggested "M+" and such which
were rejected because Porcelains and people's scripts depended
deeply on "diff --name-status" output being stable.
prev parent reply other threads:[~2006-10-25 22:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-24 1:59 [PATCH] Fix bad usage of mkpath in builtin-branch.sh Lars Hjemli
2006-10-24 6:46 ` Junio C Hamano
2006-10-24 11:38 ` Petr Baudis
2006-10-25 4:00 ` Junio C Hamano
2006-10-25 4:46 ` Junio C Hamano
2006-10-25 22:43 ` Petr Baudis
2006-10-25 22:51 ` Junio C Hamano [this message]
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=7v3b9cko0b.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/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).