From: Junio C Hamano <gitster@pobox•com>
To: Linus Arver <linusarver@gmail•com>
Cc: git@vger•kernel.org
Subject: Re: [PATCH 4/7] Documentation: git-init: --separate-git-dir: clarify
Date: Tue, 05 Aug 2014 15:12:21 -0700 [thread overview]
Message-ID: <xmqqiom6oabe.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1407002817-29221-5-git-send-email-linusarver@gmail.com> (Linus Arver's message of "Sat, 2 Aug 2014 11:06:54 -0700")
Linus Arver <linusarver@gmail•com> writes:
> Signed-off-by: Linus Arver <linusarver@gmail•com>
> ---
You would need to work on your justification skills ;-) in the log
message. What does this change "clarify" and in what way?
> Documentation/git-init.txt | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/Documentation/git-init.txt b/Documentation/git-init.txt
> index f21b85b..bf0a7ae 100644
> --- a/Documentation/git-init.txt
> +++ b/Documentation/git-init.txt
> @@ -57,12 +57,12 @@ DIRECTORY" section below.)
>
> --separate-git-dir=<git dir>::
>
> -Instead of initializing the repository where it is supposed to be,
> -place a filesytem-agnostic Git symbolic link there, pointing to the
> -specified path, and initialize a Git repository at the path. The
> -result is Git repository can be separated from working tree. If this
> -is reinitialization, the repository will be moved to the specified
> -path.
> +Separate the Git repository from your working tree. Instead of initializing the
> +repository as a directory to either `$GIT_DIR` or `./.git/`, create a text file
> +there containing the path to the actual repository. This file acts as
> +filesystem-agnostic Git symbolic link to the repository.
> ++
> +If this is reinitialization, the repository will be moved to the specified path.
>
> --shared[=(false|true|umask|group|all|world|everybody|0xxx)]::
next prev parent reply other threads:[~2014-08-05 22:12 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 [this message]
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 ` [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=xmqqiom6oabe.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=linusarver@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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