git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Alan Chandler <alan@chandlerfamily.org.uk>, git@vger.kernel.org
Subject: Re: Newbie falls at first hurdle
Date: Sun, 18 Sep 2005 10:54:20 -0700	[thread overview]
Message-ID: <7vzmqa2reb.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0509181033520.26803@g5.osdl.org> (Linus Torvalds's message of "Sun, 18 Sep 2005 10:40:06 -0700 (PDT)")

Linus Torvalds <torvalds@osdl.org> writes:

> In other words, you'd have to explain what "pu^2~3" means.
>
> And octopus merges, for that matter. I don't think the tutorial ever 
> explains those.

Sorry, my excuses are (1) I just did a quick example from a tree
I had handy -- my live tree; (2) as long as the user knows the
commit show-branch labeled with the cryptic "pu^2~3" is the one
s/he wants, it does not matter much what that label exactly
means.

But of course you are right.

  reply	other threads:[~2005-09-18 17:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-17 12:09 Newbie falls at first hurdle Alan Chandler
2005-09-17 16:13 ` Junio C Hamano
2005-09-17 16:30   ` Alan Chandler
2005-09-17 16:50     ` Junio C Hamano
2005-09-17 17:01       ` Alan Chandler
2005-09-18  1:35 ` Horst von Brand
2005-09-18 10:54   ` Martin Langhoff
2005-09-18 12:47     ` Alan Chandler
2005-09-18 17:22       ` Junio C Hamano
2005-09-18 17:40         ` Linus Torvalds
2005-09-18 17:54           ` Junio C Hamano [this message]
2005-09-18 19:11         ` Alan Chandler
2005-09-18 20:10           ` Junio C Hamano
2005-09-19 19:09           ` Sven Verdoolaege
2005-09-18 19:06       ` Martin Langhoff
2005-09-18 14:59 ` Petr Baudis
2005-09-18 17:35   ` Junio C Hamano
2005-09-18 19:09     ` [PATCH] Improve git-update-index error reporting Petr Baudis

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=7vzmqa2reb.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=alan@chandlerfamily.org.uk \
    --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 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).