From: Junio C Hamano <gitster@pobox•com>
To: Philip Oakley <philipoakley@iee•org>
Cc: GitList <git@vger•kernel.org>,
Jonathan Nieder <jrnieder@gmail•com>,
Felipe Contreras <felipe.contreras@gmail•com>
Subject: Re: [PATCH V2 3/3] doc: command line interface (cli) dot-repository dwimmery
Date: Fri, 13 Sep 2013 15:31:50 -0700 [thread overview]
Message-ID: <xmqqy570gxpl.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1379107397-964-4-git-send-email-philipoakley@iee.org> (Philip Oakley's message of "Fri, 13 Sep 2013 22:23:17 +0100")
Philip Oakley <philipoakley@iee•org> writes:
> The Git cli will accept dot '.' (period) as the relative path
> to the current repository. Explain this action.
>
> Signed-off-by: Philip Oakley <philipoakley@iee•org>
> ---
> Documentation/gitcli.txt | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/Documentation/gitcli.txt b/Documentation/gitcli.txt
> index 7d54b77..b065c0e 100644
> --- a/Documentation/gitcli.txt
> +++ b/Documentation/gitcli.txt
> @@ -58,6 +58,10 @@ the paths in the index that match the pattern to be checked out to your
> working tree. After running `git add hello.c; rm hello.c`, you will _not_
> see `hello.c` in your working tree with the former, but with the latter
> you will.
> ++
> +Just as the filesystem '.' (period) refers to the current directory,
> +using a '.' as a repository name in Git (a dot-repository) is a relative
> +path for your current repository.
Looks good to me. Thanks.
prev parent reply other threads:[~2013-09-13 22:31 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-19 11:54 [RFC/PATCH 0/2] Extend dot repository documentation Philip Oakley
2013-05-19 11:54 ` [RFC/PATCH 1/2] config doc: add dot-repository note Philip Oakley
2013-05-19 17:43 ` Jonathan Nieder
2013-05-20 17:50 ` Junio C Hamano
2013-05-20 21:10 ` Philip Oakley
2013-05-19 11:54 ` [RFC/PATCH 2/2] doc: command line interface (cli) dot-repository dwimmery Philip Oakley
2013-05-19 17:39 ` Jonathan Nieder
2013-05-19 22:29 ` Philip Oakley
2013-05-20 17:55 ` Junio C Hamano
2013-05-20 21:09 ` Philip Oakley
2013-05-20 22:22 ` Junio C Hamano
2013-05-21 7:47 ` Philip Oakley
2013-05-21 16:23 ` Junio C Hamano
2013-05-21 21:21 ` Felipe Contreras
2013-05-21 22:33 ` Philip Oakley
2013-05-21 23:03 ` Felipe Contreras
2013-05-21 23:24 ` Junio C Hamano
2013-05-22 0:27 ` Felipe Contreras
2013-05-22 0:50 ` Junio C Hamano
2013-05-22 2:57 ` Felipe Contreras
2013-05-22 16:50 ` Junio C Hamano
2013-05-22 22:12 ` Felipe Contreras
2013-05-22 22:09 ` Philip Oakley
2013-05-22 22:15 ` Felipe Contreras
2013-09-13 21:23 ` [PATCH V2 0/3] Extend dot repository documentation Philip Oakley
2013-09-13 21:23 ` [PATCH V2 1/3] Doc URLs: relative paths imply the dot-respository Philip Oakley
2013-09-13 22:21 ` Junio C Hamano
2013-09-14 20:47 ` Philip Oakley
2013-09-13 21:23 ` [PATCH V2 2/3] config doc: update dot-repository notes Philip Oakley
2013-09-13 22:28 ` Junio C Hamano
2013-09-14 20:47 ` Philip Oakley
2013-09-13 21:23 ` [PATCH V2 3/3] doc: command line interface (cli) dot-repository dwimmery Philip Oakley
2013-09-13 22:31 ` Junio C Hamano [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=xmqqy570gxpl.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=felipe.contreras@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=jrnieder@gmail$(echo .)com \
--cc=philipoakley@iee$(echo .)org \
/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