From: Junio C Hamano <gitster@pobox.com>
To: Linus Arver <linusarver@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 7/7] Documentation: git-init: flesh out example
Date: Tue, 05 Aug 2014 15:14:48 -0700 [thread overview]
Message-ID: <xmqqegwuoa7b.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1407002817-29221-8-git-send-email-linusarver@gmail.com> (Linus Arver's message of "Sat, 2 Aug 2014 11:06:57 -0700")
Linus Arver <linusarver@gmail.com> writes:
> Signed-off-by: Linus Arver <linusarver@gmail.com>
> ---
> Documentation/git-init.txt | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/git-init.txt b/Documentation/git-init.txt
> index b94d165..16e9f9c 100644
> --- a/Documentation/git-init.txt
> +++ b/Documentation/git-init.txt
> @@ -138,10 +138,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>
I agree it is a good discipline to make the initial "pristine"
import immediately after "git add ." without doing anything else.
Perhaps the description below wants to make it more explicit?
> ----------------
> +
> -<1> prepare /path/to/my/codebase/.git directory
> -<2> add all existing file to the index
> +<1> Create a /path/to/my/codebase/.git directory.
> +<2> Add all existing files to the index.
> +<3> Create the first root-commit.
>
> GIT
> ---
next prev parent reply other threads:[~2014-08-05 22:15 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 [this message]
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 ` [PATCH v2 7/7] Documentation: git-init: flesh out example Linus Arver
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=xmqqegwuoa7b.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=linusarver@gmail.com \
/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.