Git development
 help / color / mirror / Atom feed
From: Nicolas Pitre <nico@cam.org>
To: Petr Baudis <pasky@ucw.cz>
Cc: Linus Torvalds <torvalds@osdl.org>,
	Junio C Hamano <junkio@cox.net>,
	git@vger.kernel.org
Subject: Re: [PATCH] add a diff-files command (revised)
Date: Wed, 27 Apr 2005 22:39:00 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.62.0504272229290.14033@localhost.localdomain> (raw)
In-Reply-To: <20050428021547.GB8612@pasky.ji.cz>

On Thu, 28 Apr 2005, Petr Baudis wrote:

> Dear diary, on Thu, Apr 28, 2005 at 04:06:29AM CEST, I got a letter
> where Nicolas Pitre <nico@cam.org> told me that...
> > In the same spirit as diff-tree and diff-cache, here is a diff-files 
> > command that processes differences between the index cache and the 
> > working directory content.  It produces lists of files that are either 
> > changed, deleted and/or unknown with regards to the current cache, 
> > content. The -p option can also be used to generate a patch describing 
> > the differences in patch form.
> 
> Except some usage enhancement, how does this differ from show-diff?

This is intended to supercede show-diff.  But since its argument list is 
different I thought creating a new command would be nicer while 
show-diff usage (which has accumulated cruft already with now unused 
switches) is phased out.  Also the name "diff-files" is more inline with 
the other diff commands.

> Also, for some reason you have update-cache.c in your patch too.

Huh!?


Nicolas

      reply	other threads:[~2005-04-28  2:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-28  2:06 [PATCH] add a diff-files command (revised) Nicolas Pitre
2005-04-28  2:15 ` Petr Baudis
2005-04-28  2:39   ` Nicolas Pitre [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=Pine.LNX.4.62.0504272229290.14033@localhost.localdomain \
    --to=nico@cam.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=pasky@ucw.cz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox