All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Carl Worth <cworth@cworth.org>
Cc: git@vger.kernel.org
Subject: Re: A tour of git: the basics (and notes on some unfriendly messages)
Date: Fri, 28 Sep 2007 17:45:30 -0700	[thread overview]
Message-ID: <7v1wcinvth.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <87ir5us82a.wl%cworth@cworth.org> (Carl Worth's message of "Fri, 28 Sep 2007 16:07:25 -0700")

Thanks for starting this.  It was an interesting read.

----------------------------------------------------------------

#2.2.1

"git help init" would give man page.  The time when the short
help is given is when you mistype options, as in:

	$ git init --huh?

#2.4

	By default this command prints a brief paragraph of output...

Not really.  The default is to give you the entire log message,
unless you somehow made --pretty=short the default with your
copy of git.

	The "git log" tool doesn't display the Committer...

You can ask it to, so "by default" is missing.

#2.7.1

	But some poepl, (notably Linus...

typo.

#2.7.6

	for which "git commit --amend" was

was what?  "invented" perhaps?


#2.8.3

	Using "git remote" to pull changes other repositories

"changes from other repositories".

----------------------------------------------------------------

  parent reply	other threads:[~2007-09-29  0:45 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-28 23:07 A tour of git: the basics (and notes on some unfriendly messages) Carl Worth
2007-09-29  0:00 ` Shawn O. Pearce
2007-09-29  0:49   ` Johannes Schindelin
2007-09-29  7:44     ` Steffen Prohaska
2007-09-29 15:06       ` Johannes Schindelin
2007-09-29 16:06         ` Steffen Prohaska
2007-09-29 16:05           ` [PATCH] WinGit: included /bin/start in the installer Steffen Prohaska
2007-09-29 16:05             ` [PATCH] WinGit: include html pages from official git.git's html branch Steffen Prohaska
2007-09-29 20:50               ` Johannes Schindelin
2007-09-29 22:13                 ` Junio C Hamano
2007-09-29 23:23                   ` Johannes Schindelin
2007-09-30  8:19                     ` Steffen Prohaska
2007-09-29  9:01   ` A tour of git: the basics (and notes on some unfriendly messages) Pierre Habouzit
2007-09-29 10:45     ` [RFC] patch series to sketch a less verbose and frightening output Pierre Habouzit
2007-09-29 10:49       ` Pierre Habouzit
     [not found]       ` <1191062758-30631-2-git-send-email-madcoder@debian.org>
2007-09-29 14:33         ` [PATCH 1/4] Rework progress module so that it uses less screen lines, with progress bars Nicolas Pitre
2007-09-29 16:07           ` Pierre Habouzit
2007-09-30 12:45     ` A tour of git: the basics (and notes on some unfriendly messages) Wincent Colaiuta
2007-09-30 13:49       ` Pierre Habouzit
2007-09-30 14:31         ` Wincent Colaiuta
2007-09-29 21:48   ` Steffen Prohaska
2007-09-29 22:25     ` Junio C Hamano
2007-09-30  8:15       ` Steffen Prohaska
2007-09-30 10:17         ` Junio C Hamano
2007-09-30 12:44         ` Johannes Schindelin
2007-09-30 13:41           ` Steffen Prohaska
2007-09-29  0:45 ` Junio C Hamano [this message]
2007-09-30  3:38   ` Carl Worth
2007-09-30  3:38   ` Carl Worth
2007-09-29  5:32 ` Nguyen Thai Ngoc Duy

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=7v1wcinvth.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=cworth@cworth.org \
    --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 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.