On Sat, 23 Apr 2005, Petr Baudis wrote:
> Note that Cogito almost actually does not use show-diff anymore.
> I'm doing diff-cache now, since that is what matters to me.

Indeed.  "diff-tree" (between releases) and "diff-cache" (between a
release and the current state) are clearly much more fundamental

Also, they have absolutely zero policy, and they're designed to be used
with the same scripting engines (ie hopefully you can use just one tool to
show the output of either in whatever format you want).

They show you what the canonical names and associated information is, and
that's it. What you _do_ with them ends up being outside the scope of git,
exactly like it should be. Details like "what format of diff" to produce 
should be left to the tools around it.

In contrast, "show-diff" was _literally_ written to check what the
difference between the "real" file and a "sha1"  file was, back when I
couldn't write the sha1 files correctly (ie I corrupted anything that 
didn't fit in the first "[un]compression block", and then calling "diff" 
to show the difference between the original and the regenerated data was 
very important).

So "show-diff" just kind of expanded from an early debugging tool to
something that _almost_ looks like a real tool. But it's absolutely the
right thing to use "diff-tree" and "diff-cache" instead.

To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to