From: Junio C Hamano <junkio@cox.net>
To: Santi <sbejar@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Ouput of git diff with <ent>:<path>
Date: Tue, 16 May 2006 15:44:17 -0700 [thread overview]
Message-ID: <7vwtcl4mke.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <8aa486160605161524j5d7e672eo@mail.gmail.com> (sbejar@gmail.com's message of "Wed, 17 May 2006 00:24:12 +0200")
Santi <sbejar@gmail.com> writes:
> ... I didn't expect the rename from/to neither the
> similarity index 0%.
>
> diff --git a/v1.3.3:Makefile b/Makefile
> similarity index 0%
> rename from v1.3.3:Makefile
> rename to Makefile
> index b808eca..55d1937 100644
> --- a/v1.3.3:Makefile
> +++ b/Makefile
Yes I am aware of this one; I just haven't bothered to deal with
it.
It looks at two strings, "v1.3.3:Makefile" and "Makefile", and
says "they have different names -- they are renamed".
Patches welcome as long as you do not break more usual cases
;-).
prev parent reply other threads:[~2006-05-16 22:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 22:24 Ouput of git diff with <ent>:<path> Santi
2006-05-16 22:44 ` 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=7vwtcl4mke.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=sbejar@gmail.com \
/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).