git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Philip Oakley <philipoakley@iee.org>
To: GitList <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>
Subject: [PATCH V3 0/2] Extend dot repository documentation
Date: Sat, 21 Sep 2013 16:11:07 +0100	[thread overview]
Message-ID: <1379776269-4496-1-git-send-email-philipoakley@iee.org> (raw)

This completes the patch series on adding short notes about
the dot repository capability in git, which is a consequence of
the relative path '.' being used as a repository URL.

The previous 2/3 was accepted and is not repeated here.
Patch 3/3 is now an ammendment 1/2 
Patch 1/3 is corrected and is now 2/2

The first patch is a minor update that give the dot repository note
its own bullet, and updates the wording to imply repository discovery
from the current directory.

The second patch updates the Git URLs section to include a specific
note about relative paths and its use as a dot repository.

It should be noted that repository discovery is not well covered in
the documentation but is distributed among a number sections. This
could do with a small section somewhere..

Philip Oakley (2):
  doc: command line interface (cli) dot-repository dwimmery
  Doc URLs: relative paths imply the dot-respository

 Documentation/gitcli.txt | 8 ++++----
 Documentation/urls.txt   | 8 ++++++++
 2 files changed, 12 insertions(+), 4 deletions(-)

-- 
1.8.1.msysgit.1

             reply	other threads:[~2013-09-21 15:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-21 15:11 Philip Oakley [this message]
2013-09-21 15:11 ` [PATCH V3 1/2] doc: command line interface (cli) dot-repository dwimmery Philip Oakley
2013-10-15 21:57   ` Junio C Hamano
2013-10-16  6:53     ` Philip Oakley
2013-09-21 15:11 ` [PATCH V3 2/2] Doc URLs: relative paths imply the dot-respository Philip Oakley

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=1379776269-4496-1-git-send-email-philipoakley@iee.org \
    --to=philipoakley@iee.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jrnieder@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 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).