git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Andy Parkins <andyparkins@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-show --stat on first commit
Date: Fri, 24 Nov 2006 08:49:53 +0100	[thread overview]
Message-ID: <200611240849.53510.jnareb@gmail.com> (raw)
In-Reply-To: <200611230925.07821.andyparkins@gmail.com>

Andy Parkins wrote:
> On Tuesday 2006 November 21 20:03, Jakub Narebski wrote:
> 
>> We don't show patch for merges by default in git-show, so I don't
>> see why we would want to show root commit diff in git-show by default:
>> those two are very similar.
> 
> $ git init-db
> $ date > file1
> $ git add file1; git commit -a -m "file1 added"
> $ date > file2
> $ git add file2; git commit -a -m "file2 added"
> $ git show --stat HEAD
> $ git show --stat HEAD^
> 
> I can understand while people get confused.  Two patches, both add a file.  
> git-show on one of them shows a stat; on the other it doesn't.

Well, perhaps "git show --stat" should show diffstat also for root
commit, because it shows diffstat for merges (although not patch),
but not patch (which usually is huge).
-- 
Jakub Narebski

  reply	other threads:[~2006-11-24  7:48 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-21 13:41 git-show --stat on first commit Andy Parkins
2006-11-21 14:01 ` Jakub Narebski
2006-11-21 14:09 ` Santi Béjar
2006-11-21 16:08   ` Peter Baumann
2006-11-21 16:18     ` Jakub Narebski
2006-11-21 17:16       ` Peter Baumann
2006-11-21 18:14       ` Horst H. von Brand
2006-11-21 16:31     ` Linus Torvalds
2006-11-21 16:47       ` Shawn Pearce
2006-11-21 17:11       ` Peter Baumann
2006-11-21 17:20         ` Linus Torvalds
2006-11-21 18:38         ` Olivier Galibert
2006-11-21 18:42           ` Shawn Pearce
2006-11-21 19:05           ` Petr Baudis
2006-11-21 18:06       ` Petr Baudis
2006-11-21 18:16         ` Jakub Narebski
2006-11-21 18:21           ` Petr Baudis
2006-11-21 18:34             ` Shawn Pearce
2006-11-21 18:39             ` Andy Parkins
2006-11-21 18:48               ` Petr Baudis
2006-11-21 18:52                 ` Shawn Pearce
2006-11-21 19:04                   ` Petr Baudis
2006-11-21 19:31             ` Junio C Hamano
2006-11-21 20:03               ` Jakub Narebski
2006-11-23  9:25                 ` Andy Parkins
2006-11-24  7:49                   ` Jakub Narebski [this message]
2006-11-23  9:36               ` [PATCH] config option core.showroot to enable showing the diff of the root commit Peter Baumann
2006-11-23 20:52                 ` Junio C Hamano
2006-11-23 23:34                   ` Peter Baumann
2006-11-24  0:18                     ` Junio C Hamano
2006-11-24  1:30                       ` Junio C Hamano
2006-11-24  7:53                         ` Peter Baumann
2006-11-24  8:54                           ` Junio C Hamano
2006-11-24  9:04                             ` Peter Baumann
2006-11-21 18:39       ` git-show --stat on first commit Carl Worth
2006-11-21 19:15       ` 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=200611240849.53510.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=andyparkins@gmail.com \
    --cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).