All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Grégoire Paris" <gregoire.paris.greg0ire@gmail.com>
To: git@vger.kernel.org
Cc: "Grégoire Paris" <postmaster@greg0ire.fr>
Subject: [PATCH] Document dotfiles exclusion on template copy
Date: Sat, 18 Feb 2017 00:37:00 +0100	[thread overview]
Message-ID: <20170217233700.14643-1-postmaster@greg0ire.fr> (raw)

Since there is no dotfile in the default template directory, there was
no point in making the check for . or .. more accurate when copying. Now
that you can customize the template directory, it would make sense, but
it's actually a good thing to at this because you would not want to have
your git directory copied in every git directory that is created should
you decide to put your template directory under version control. Plus, it
might be used as a feature by people who would want to exclude some
files.

Signed-off-by: Grégoire Paris <postmaster@greg0ire.fr>
---
Here is a better version.
 Documentation/git-init.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/git-init.txt b/Documentation/git-init.txt
index 9d27197..3c5a67f 100644
--- a/Documentation/git-init.txt
+++ b/Documentation/git-init.txt
@@ -116,8 +116,8 @@ does not exist, it will be created.
 TEMPLATE DIRECTORY
 ------------------
 
-The template directory contains files and directories that will be copied to
-the `$GIT_DIR` after it is created.
+Files and directories in the template directory whose name do not start with a
+dot will be copied to the `$GIT_DIR` after it is created.
 
 The template directory will be one of the following (in order):
 
-- 
2.9.3


             reply	other threads:[~2017-02-17 23:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-17 23:37 Grégoire Paris [this message]
2017-02-17 23:59 ` [PATCH] Document dotfiles exclusion on template copy Junio C Hamano
  -- strict thread matches above, loose matches on Subject: below --
2017-02-17 23:27 Grégoire Paris
2017-02-17 23:32 ` Grégoire PARIS

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=20170217233700.14643-1-postmaster@greg0ire.fr \
    --to=gregoire.paris.greg0ire@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=postmaster@greg0ire.fr \
    /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.