git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcus Comstedt <marcus@mc.pp.se>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Lars Hjemli <hjemli@gmail.com>, git@vger.kernel.org
Subject: Re: git log --stat FILE
Date: Sun, 08 Aug 2010 15:33:02 +0200	[thread overview]
Message-ID: <yf9ocddut4h.fsf@chiyo.mc.pp.se> (raw)
In-Reply-To: <201008081508.53732.jnareb@gmail.com> (Jakub Narebski's message of "Sun, 8 Aug 2010 15:08:53 +0200")


Jakub Narebski <jnareb@gmail.com> writes:

> To me (and probably many others), a "diff" is something that describe
> differences between two versions (compares two version).

Jakub, there is no need for you to explain or justify why this is
obvious to you.  I have no problem accepting that at face value.
I'm simply trying to explain why this was not obvious to me, in the
hope of aiding any effort in improving the documentation.  After all,
writing documentation for something you feel is obvious is very
difficult.  But if you feel that the documentation is fine as it is,
that is also your privilege.


> Note that 'GNU diff' (and other "/usr/bin/diff") supports three
> output formats:  ed based, context and unified formats.

Indeed, and all those qualify as "diffs" in my mindset.  I would
however not consider the output of "diff -q" as a true "diff", and
naturally not the output of "diff --version".


  // Marcus

  reply	other threads:[~2010-08-08 13:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-08 11:29 git log --stat FILE Marcus Comstedt
2010-08-08 11:54 ` Jakub Narebski
2010-08-08 11:54 ` Lars Hjemli
2010-08-08 12:04   ` Marcus Comstedt
2010-08-08 12:26     ` Jakub Narebski
2010-08-08 12:35       ` Marcus Comstedt
2010-08-08 13:08         ` Jakub Narebski
2010-08-08 13:33           ` Marcus Comstedt [this message]
2010-08-08 15:31             ` [PATCH] Documentation/git-log: Clarify --full-diff Michael J Gruber
2010-08-09  7:45               ` Matthieu Moy
2010-08-09 19:57                 ` 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=yf9ocddut4h.fsf@chiyo.mc.pp.se \
    --to=marcus@mc.pp.se \
    --cc=git@vger.kernel.org \
    --cc=hjemli@gmail.com \
    --cc=jnareb@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).