mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Robert P. J. Day" <>
To: Git Mailing list <>
Subject: does a new repo actually *need* default template content?
Date: Mon, 28 May 2018 09:00:00 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.21.1805280836140.10191@localhost.localdomain> (raw)

[-- Attachment #1: Type: text/plain, Size: 2136 bytes --]

  (apologies for more pedantic nitpickery, just little things i'm
running across in my travels. aside: i actually teach git courses, so
it's a bit embarrassing that i don't know some of this stuff. *sigh*.)

  running on fully-updated fedora 28 system:

  $ git --version
  git version 2.17.0

  is there anything in /usr/share/git-core/templates/ that is actually
*essential* when initializing a new repo? this is what's in my
directory by that name:

  ├── branches
  ├── description
  ├── hooks
  │   ├── applypatch-msg.sample
  │   ├── commit-msg.sample
  │   ├── fsmonitor-watchman.sample
  │   ├── post-update.sample
  │   ├── pre-applypatch.sample
  │   ├── pre-commit.sample
  │   ├── prepare-commit-msg.sample
  │   ├── pre-push.sample
  │   ├── pre-rebase.sample
  │   ├── pre-receive.sample
  │   └── update.sample
  └── info
      └── exclude

but none of that above looks critically important.

  "man gitrepository-layout" describes the "branches" directory as
"slightly deprecated", the default description file has a generic
"Unnamed repository" message but, hey, so does the git source code
repo itself, the hooks are all "commented out", and the info/exclude
file effectively has no content, so i'm guessing that nothing there
actually needs to be used to populate a new repo via "git init",

  under the circumstances, then, should it be a viable option to
initialize a new repo while specifying you want *no* initial template
content? it appears you can do that just by specifying a bogus
template directory (or even /dev/null) with "--template=", but that
generates a "warning" -- does a selection like that even merit a
"warning" if it's clear that's what i'm trying to do?



Robert P. J. Day                                 Ottawa, Ontario, CANADA


             reply	other threads:[~2018-05-28 13:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-28 13:00 Robert P. J. Day [this message]
2018-05-28 17:56 ` does a new repo actually *need* default template content? Ævar Arnfjörð Bjarmason
2018-06-01  7:06   ` Jeff King
2018-06-01 14:38     ` Santiago Torres

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LFD.2.21.1805280836140.10191@localhost.localdomain \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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 read-only IMAP folder(s) and NNTP newsgroup(s).