All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ramkumar Ramachandra <artagnon@gmail.com>
To: git@vger.kernel.org
Subject: [PATCH] Update documentation: git-commit is not a shell command
Date: Sat, 16 Jan 2010 15:05:40 +0530	[thread overview]
Message-ID: <f3271551001160135k569e2692i5e2ab893701e1738@mail.gmail.com> (raw)

Reported by Osamu Aoki through http://bugs.debian.org/560795

Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.com>
---
 Documentation/gitcore-tutorial.txt |    9 +--------
 1 files changed, 1 insertions(+), 8 deletions(-)

diff --git a/Documentation/gitcore-tutorial.txt
b/Documentation/gitcore-tutorial.txt
index f762dca..ebc5d0b 100644
--- a/Documentation/gitcore-tutorial.txt
+++ b/Documentation/gitcore-tutorial.txt
@@ -454,14 +454,7 @@ will be pruned out, and the rest will be used as
the commit message for
 the change. If you decide you don't want to commit anything after all at
 this point (you can continue to edit things and update the index), you
 can just leave an empty message. Otherwise `git commit` will commit
-the change for you.
-
-You've now made your first real git commit. And if you're interested in
-looking at what `git commit` really does, feel free to investigate:
-it's a few very simple shell scripts to generate the helpful (?) commit
-message headers, and a few one-liners that actually do the
-commit itself ('git-commit').
-
+the change for you. You've now made your first real git commit.

 Inspecting Changes
 ------------------
-- 
1.6.5

             reply	other threads:[~2010-01-16  9:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-16  9:35 Ramkumar Ramachandra [this message]
2010-01-16 17:31 ` [PATCH] Update documentation: git-commit is not a shell command Junio C Hamano
2010-01-16 18:07   ` Ramkumar Ramachandra

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=f3271551001160135k569e2692i5e2ab893701e1738@mail.gmail.com \
    --to=artagnon@gmail.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 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.