From: Darrin Thompson <darrint@progeny.com>
To: git@vger.kernel.org
Subject: Re: Tutorial problem a/a a/b
Date: Thu, 28 Jul 2005 16:15:13 -0500 [thread overview]
Message-ID: <1122585313.12374.16.camel@localhost.localdomain> (raw)
In-Reply-To: <1122582005.12374.6.camel@localhost.localdomain>
On Thu, 2005-07-28 at 15:20 -0500, Darrin Thompson wrote:
> In the tutorial the user is instructed to create two files: a and b.
>
> Then when the user diffs the files, they see this:
>
> diff --git a/a b/a
>
> That really confused somebody and I had to untangle their brain. :-) I
> don't have a patch for it, but thought I'd point out: perhaps a and b
> aren't the best example filenames given git's diff format. :-D
>
Note: I've been fielding a few questions while some Progeny folks get up
to speed on git.
I had to explain what was meant by <tree-ish> in some usage messages.
Perhaps those should be spelled out as "tree, tag, or commit id"?
[Sorry this is a whine and not a patch.]
--
Darrin
next prev parent reply other threads:[~2005-07-28 21:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 20:20 Tutorial problem a/a a/b Darrin Thompson
2005-07-28 21:15 ` Darrin Thompson [this message]
2005-07-29 5:35 ` Junio C Hamano
2005-07-29 14:07 ` Darrin Thompson
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=1122585313.12374.16.camel@localhost.localdomain \
--to=darrint@progeny.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).