All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@ucw.cz>
To: git@vger.kernel.org
Subject: git-diff-tree -B broken
Date: Sun, 9 Apr 2006 02:46:05 +0200	[thread overview]
Message-ID: <20060409004605.GU27689@pasky.or.cz> (raw)

  Hi,

  no pun intended in the $SUBJ, but git-diff-tree -B seems to be giving
me bogus output

	$ git-diff-tree -r -p -B -M 916d8240bfc8ef5b80780b1a32ebb83ed055a178 \
		3c9324ea16c345fc0bc0f11041905ba714797e4a cg-mkpatch
	diff --git a/cg-mkpatch b/cg-mkpatch
	dissimilarity index 57%
	index 74fe917..c932bc9 100755
	--- cg-mkpatch
	+++ cg-mkpatch
	@@ -0,0 +0,0 @@

and nothing else. I'm too tired to debug or bisect this (xdiff
introduction is the obvious suspect, I guess), just didn't want this
to slip into the looming 1.3.0 so reporting early.

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
Right now I am having amnesia and deja-vu at the same time.  I think
I have forgotten this before.

             reply	other threads:[~2006-04-09  0:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-09  0:46 Petr Baudis [this message]
2006-04-09  2:51 ` git-diff-tree -B broken Junio C Hamano
2006-04-09  3:30   ` [PATCH] diffcore-rename: fix merging back a broken pair Junio C Hamano

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=20060409004605.GU27689@pasky.or.cz \
    --to=pasky@ucw.cz \
    --cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.