All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Linus Torvalds <torvalds@osdl.org>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: change of git-diff-tree and symlinks
Date: Thu, 26 May 2005 00:26:22 +0200	[thread overview]
Message-ID: <20050525222622.GA8552@vrfy.org> (raw)
In-Reply-To: <7vzmujjdq4.fsf@assigned-by-dhcp.cox.net>

On Wed, May 25, 2005 at 12:40:51PM -0700, Junio C Hamano wrote:
> >>>>> "KS" == Kay Sievers <kay.sievers@vrfy.org> writes:
> 
> KS> Ok, works again. Any reason not to mark it as 'M'? It's easyly to
> KS> distinguish between a content change and a mode change by looking if
> KS> the sha has changed.
> 
> I'd need some time to think about this in the evening (I'm at
> work now) but I think Linus did '?' as an interim measure.  I
> suspect 'M' would work just as well without introducing a new
> class 'T', but on the other hand having them distinct would be
> easier for people who read diff-raw format, so my knee-jerk
> reaction is that we should use 'T'.  It's the same reasoning to
> have N, D, and U --- they can be gleaned by looking at mode and
> sha fields and there is no need to mark them any differently but
> surely marking them the way we do now is much nicer.

If we introduce 'T', how is a content _and_ a type change represented
if they happen at the same time?

Kay


  parent reply	other threads:[~2005-05-25 22:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-25 11:17 change of git-diff-tree and symlinks Kay Sievers
2005-05-25 18:08 ` Linus Torvalds
2005-05-25 18:35   ` Kay Sievers
2005-05-25 19:40     ` Junio C Hamano
2005-05-25 22:06       ` [PATCH] Adjust show-files test for dotfiles Junio C Hamano
2005-05-25 22:07       ` [PATCH] Fix type-change handling when assigning the status code to filepairs Junio C Hamano
2005-05-25 22:26       ` Kay Sievers [this message]
2005-05-25 22:43         ` change of git-diff-tree and symlinks Junio C Hamano
2005-05-25 22:47         ` Linus Torvalds
2005-05-25 23:00           ` [PATCH] Mode only changes from diff Junio C Hamano
2005-05-26  2:11             ` [PATCH] Test case portability fix Junio C Hamano
2005-05-26  2:36               ` Linus Torvalds
2005-05-26  2:55                 ` Junio C Hamano
2005-05-29 14:16 ` change of git-diff-tree and symlinks Jochen Roemling
2005-05-29 15:06   ` Kay Sievers
2005-05-29 16:06     ` Jochen Roemling
2005-05-29 16:14       ` Sebastian Kuzminsky
2005-05-30  3:17       ` Sebastian Kuzminsky
2005-05-29 18:55     ` Junio C Hamano
2005-05-29 21:32     ` Petr Baudis

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=20050525222622.GA8552@vrfy.org \
    --to=kay.sievers@vrfy.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=torvalds@osdl.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.