git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avery Pennarun <apenwarr@gmail.com>
To: Jay Soffian <jaysoffian@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
	"David Martínez Martí" <desarrollo@gestiweb.com>,
	git@vger.kernel.org, deavidsedice@gmail.com
Subject: Re: Possible bug in Git
Date: Thu, 15 Apr 2010 20:45:55 -0400	[thread overview]
Message-ID: <u2t32541b131004151745k5284b05egfcbbd29d69bd9d94@mail.gmail.com> (raw)
In-Reply-To: <o2w76718491004151738zb2deaad1p3f7360a437725c4d@mail.gmail.com>

On Thu, Apr 15, 2010 at 8:38 PM, Jay Soffian <jaysoffian@gmail.com> wrote:
> On Thu, Apr 15, 2010 at 8:13 PM, Avery Pennarun <apenwarr@gmail.com> wrote:
>>  true >profile   # blank the file
>>  git commit -a -m resolved
>>  git show HEAD:profile
>>   # no output
>
> Well, I wouldn't expect output from show HEAD:profile. But this is odd::
>
> $ git diff HEAD^1 --name-status
> M       profile
>
> $ git diff HEAD^2 --name-status
> M       profile
>
> $ git diff-tree HEAD --name-status
> <no output>
>
> Hmfph. "git log -m -p -1" at least gives the diffs from each side.

Whoops, actually I meant "git show HEAD profile".  Totally different,
of course.  But it doesn't produce output either :)

Have fun,

Avery

  reply	other threads:[~2010-04-16  0:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-15 10:47 Possible bug in Git David Martínez Martí
2010-04-15 12:59 ` [PATCH] combined diff: correctly handle truncated file Thomas Rast
2010-04-15 23:45 ` Possible bug in Git Avery Pennarun
2010-04-16  0:01   ` Junio C Hamano
2010-04-16  0:06     ` Avery Pennarun
2010-04-16  0:13       ` Avery Pennarun
2010-04-16  0:38         ` Jay Soffian
2010-04-16  0:45           ` Avery Pennarun [this message]
2010-04-16 15:53         ` Linus Torvalds
2010-04-16 16:39           ` Thomas Rast
2010-04-16 16:56           ` Junio C Hamano
2010-04-16 17:00             ` Thomas Rast

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=u2t32541b131004151745k5284b05egfcbbd29d69bd9d94@mail.gmail.com \
    --to=apenwarr@gmail.com \
    --cc=deavidsedice@gmail.com \
    --cc=desarrollo@gestiweb.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jaysoffian@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).