From: Junio C Hamano <gitster@pobox.com>
To: Dmitry Potapov <dpotapov@gmail.com>
Cc: John Wiegley <johnw@newartisans.com>, git@vger.kernel.org
Subject: Re: Yet another Git tutorial
Date: Mon, 28 Apr 2008 16:34:33 -0700 [thread overview]
Message-ID: <7v63u1blkm.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080428222717.GA6160@dpotapov.dyndns.org> (Dmitry Potapov's message of "Tue, 29 Apr 2008 02:27:17 +0400")
Dmitry Potapov <dpotapov@gmail.com> writes:
> On Mon, Apr 28, 2008 at 02:39:46AM -0400, John Wiegley wrote:
>> I published another tutorial on Git today, this one describing the
>> system from a "bottom up" perspective. I know it's been written about
>> this way before, but I was aiming at a bit more thoroughness, and a
>> paced introduction to the basics.
>>
>> There's a link to the PDF is in the following blog post:
>>
>> http://www.newartisans.com/blog_files/git.from.bottom.up.php
>
> In addition to what was mentioned before me:
>
> On page 6, instead of `git show --pretty=format:%T HEAD | head -1`, it
> is better to use `git log -1 --pretty=format:'%T' HEAD`. In general,
> `git show <commit-object>` is `git log -1 -p <commit-object>`, and
> you do not need diff here.
I may be misunderstanding what the discussion is about as I was not
following the thread, but is this a contest to find the most expensive way
to spell "git rev-parse HEAD^{tree}"?
next prev parent reply other threads:[~2008-04-28 23:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 6:39 Yet another Git tutorial John Wiegley
2008-04-28 9:27 ` Johan Herland
2008-04-28 20:11 ` John Wiegley
2008-04-28 9:36 ` Jeff King
2008-04-28 16:30 ` Brian Gernhardt
2008-04-28 16:40 ` Paolo Bonzini
2008-04-28 16:42 ` Brian Gernhardt
2008-04-28 19:45 ` Bob Hiestand
2008-04-28 22:27 ` Dmitry Potapov
2008-04-28 23:34 ` Junio C Hamano [this message]
2008-04-29 0:17 ` Junio C Hamano
2008-04-29 1:25 ` Matt Graham
2008-04-30 1:40 ` John Wiegley
2008-04-30 23:17 ` Robert Haines
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=7v63u1blkm.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=dpotapov@gmail.com \
--cc=git@vger.kernel.org \
--cc=johnw@newartisans.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).