From: Linus Arver <linusarver@gmail.com>
To: git@vger.kernel.org
Cc: "Steven Drake" <sdrake@xnet.co.nz>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>,
"Johan Herland" <johan@herland.net>,
"Linus Arver" <linusarver@gmail.com>
Subject: [PATCH v2 7/7] Documentation: git-init: flesh out example
Date: Fri, 8 Aug 2014 10:29:20 -0700 [thread overview]
Message-ID: <1407518960-6203-8-git-send-email-linusarver@gmail.com> (raw)
In-Reply-To: <1407518960-6203-1-git-send-email-linusarver@gmail.com>
Add a third step `git commit` after adding files for the first time.
Signed-off-by: Linus Arver <linusarver@gmail.com>
---
Documentation/git-init.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/git-init.txt b/Documentation/git-init.txt
index 9f2c7d8..369f889 100644
--- a/Documentation/git-init.txt
+++ b/Documentation/git-init.txt
@@ -141,10 +141,12 @@ Start a new Git repository for an existing code base::
$ cd /path/to/my/codebase
$ git init <1>
$ git add . <2>
+$ git commit <3>
----------------
+
<1> Create a /path/to/my/codebase/.git directory.
<2> Add all existing files to the index.
+<3> Record the pristine state as the first commit in the history.
GIT
---
--
2.0.4
prev parent reply other threads:[~2014-08-08 17:30 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-02 18:06 [PATCH] lots of documentation fixes/rewordings in git-init(1) Linus Arver
2014-08-02 18:06 ` [PATCH 1/7] Documentation: git-init: typographical fixes Linus Arver
2014-08-05 22:06 ` Junio C Hamano
2014-08-06 4:58 ` Linus Arver
2014-08-02 18:06 ` [PATCH 2/7] Documentation: git-init: list items facelift Linus Arver
2014-08-02 18:06 ` [PATCH 3/7] Documentation: git-init: template directory: reword Linus Arver
2014-08-05 22:10 ` Junio C Hamano
2014-08-06 5:15 ` Linus Arver
2014-08-06 17:21 ` Junio C Hamano
2014-08-08 16:36 ` Linus Arver
2014-08-02 18:06 ` [PATCH 4/7] Documentation: git-init: --separate-git-dir: clarify Linus Arver
2014-08-05 22:12 ` Junio C Hamano
2014-08-06 5:21 ` Linus Arver
2014-08-06 17:35 ` Junio C Hamano
2014-08-08 16:42 ` Linus Arver
2014-08-02 18:06 ` [PATCH 5/7] Documentation: git-init: reword parenthetical statements Linus Arver
2014-08-02 18:06 ` [PATCH 6/7] Documentation: git-init: template directory: reword and cross-reference Linus Arver
2014-08-02 18:06 ` [PATCH 7/7] Documentation: git-init: flesh out example Linus Arver
2014-08-05 22:14 ` Junio C Hamano
2014-08-06 5:34 ` Linus Arver
2014-08-06 17:41 ` Junio C Hamano
2014-08-08 16:49 ` Linus Arver
2014-08-08 17:29 ` [PATCH v2] lots of documentation fixes/rewordings in git-init(1) Linus Arver
2014-08-08 17:29 ` [PATCH v2 1/7] Documentation: git-init: typographical fixes Linus Arver
2014-08-08 17:29 ` [PATCH v2 2/7] Documentation: git-init: list items facelift Linus Arver
2014-08-08 17:29 ` [PATCH v2 3/7] Documentation: git-init: template directory: reword Linus Arver
2014-08-08 17:29 ` [PATCH v2 4/7] Documentation: git-init: --separate-git-dir: clarify Linus Arver
2014-08-08 17:29 ` [PATCH v2 5/7] Documentation: git-init: reword parenthetical statements Linus Arver
2014-08-08 17:29 ` [PATCH v2 6/7] Documentation: git-init: template directory: reword and cross-reference Linus Arver
2014-08-08 17:29 ` Linus Arver [this message]
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=1407518960-6203-8-git-send-email-linusarver@gmail.com \
--to=linusarver@gmail.com \
--cc=git@vger.kernel.org \
--cc=johan@herland.net \
--cc=pclouds@gmail.com \
--cc=sdrake@xnet.co.nz \
/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).