git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@suse.cz>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-show --stat on first commit
Date: Tue, 21 Nov 2006 19:21:35 +0100	[thread overview]
Message-ID: <20061121182135.GD7201@pasky.or.cz> (raw)
In-Reply-To: <ejvfng$cj6$1@sea.gmane.org>

On Tue, Nov 21, 2006 at 07:16:44PM CET, Jakub Narebski wrote:
> Petr Baudis wrote:
> 
> > On Tue, Nov 21, 2006 at 05:31:30PM CET, Linus Torvalds wrote:
> >> git didn't end up doing that (and I'm personally pretty happy about it), 
> >> but it was one of the things I was kind of thinking about: a "git import" 
> >> kind of thing would have created an initial commit which was pre-populated 
> >> with the thing to import, and a "git init-db" would have created an 
> >> initial root commit that was empty.
> >> 
> >> That would have made the current "don't show the root diff" behaviour very 
> >> natural (and you'd still have gotten the initial diff for a new project), 
> >> but on the other hand, it would have had that annoying unnecessary "init" 
> >> commit, and you'd _still_ have wanted to have something like "--root" in 
> >> order to show the import commit as a patch (which you _sometimes_ want to 
> >> do).
> > 
> > It's being asked by users time by time (first in April last year ;) and
> > I'm not sure about any good answer I should tell them, so is the reason
> > for not doing the implicit empty commit that it would be "annoying" I
> > suppose in the log output?
> 
> git repo-config show.difftree --root
> git repo-config whatchanged.difftree --root

That means extra pointless setup and is besides the point anyway, I was
asking about empty commits, not default command settings.

BTW, the other frequent reason why empty commits come up so frequently
is a FAQ "how do I create an unrelated branch in my repository" - their
idea is that they will create a new branch starting with an empty commit
(of course noone would think of anything like that in inferior VCSes
because replacing the checked out trees would took forever; how cool Git
is!).

(The answer is usually "create the branch in a separate repo and then
fetch it to the original one". But it feels a bit kludgy given the
otherwise seamless support for unrelated branches. (Not that I ever was
a big fan of unrelated long-lived branches in general.))

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
The meaning of Stonehenge in Traflamadorian, when viewed from above, is:
"Replacement part being rushed with all possible speed."

  reply	other threads:[~2006-11-21 18:21 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 [this message]
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
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=20061121182135.GD7201@pasky.or.cz \
    --to=pasky@suse.cz \
    --cc=git@vger.kernel.org \
    --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).