All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olivier Galibert <galibert@pobox.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Radoslaw Szkodzinski <astralstorm@o2.pl>, git@vger.kernel.org
Subject: Re: What should I use instead of git show?
Date: Mon, 13 Mar 2006 17:58:42 +0100	[thread overview]
Message-ID: <20060313165842.GD87487@dspnet.fr.eu.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0603130830050.3618@g5.osdl.org>

On Mon, Mar 13, 2006 at 08:33:22AM -0800, Linus Torvalds wrote:
> Why not just use "git show"?
> 
> It hasn't gone anywhere that I know of. It's still there.

Oh beautiful.

I had an old (as in 3 months max, but heh) git-tree at work in a
corner from which I had compiled git.  When I saw it didn't have git
show which I have at home I did a git pull, recompile, reinstall.

The new git didn't have git show, so I thought it had been removed
after all.  Turns out, the git pull had broken halfway due to the old
version of git.  It hadn't fast forwarded _all_ the versions.  But the
new git, while not current, has been able to do the complete git pull
this time.  And now I have git show at work too.

Guess you have to update git every month or so if you want to be able
to follow current trees.

  OG.

  reply	other threads:[~2006-03-13 16:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-13 14:47 What should I use instead of git show? Olivier Galibert
2006-03-13 16:17 ` Radoslaw Szkodzinski
2006-03-13 16:33   ` Linus Torvalds
2006-03-13 16:58     ` Olivier Galibert [this message]
2006-03-13 23:26     ` Mark Hollomon
2006-03-13 23:55       ` Junio C Hamano
2006-03-14 11:49         ` Mark Hollomon
2006-03-13 16:50   ` Olivier Galibert
2006-03-20 11:33     ` Paul Mackerras
2006-03-20 13:16       ` Olivier Galibert
2006-03-14  3:09 ` 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=20060313165842.GD87487@dspnet.fr.eu.org \
    --to=galibert@pobox.com \
    --cc=astralstorm@o2.pl \
    --cc=git@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.