From: Jeff King <email@example.com> To: "Ævar Arnfjörð Bjarmason" <firstname.lastname@example.org> Cc: "Robert P. J. Day" <email@example.com>, Git Mailing list <firstname.lastname@example.org> Subject: Re: does a new repo actually *need* default template content? Date: Fri, 1 Jun 2018 03:06:10 -0400 [thread overview] Message-ID: <20180601070609.GC15578@sigill.intra.peff.net> (raw) In-Reply-To: <email@example.com> On Mon, May 28, 2018 at 07:56:12PM +0200, Ævar Arnfjörð Bjarmason wrote: > > On Mon, May 28 2018, Robert P. J. Day wrote: > > > (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*.) > > Aside from maybe the empty branches/ directory (see c8a58ac5a5 ("Revert > "Don't create the $GIT_DIR/branches directory on init"", 2009-10-31)), > none of this is needed. > > I wish we didn't create any of this stuff, but have never been inclined > to make that my hill to die on. > > I think we're much better off just shipping e.g. a single README file in > hooks/, or just nothing at all. FWIW, that's my opinion, too (including the "hill to die on" part). I also wish hooks were just shell snippets in the config files that could follow the usual config-precedence rules. -Peff
next prev parent reply other threads:[~2018-06-01 7:06 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-05-28 13:00 Robert P. J. Day 2018-05-28 17:56 ` Ævar Arnfjörð Bjarmason 2018-06-01 7:06 ` Jeff King [this message] 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: 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=20180601070609.GC15578@sigill.intra.peff.net \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: does a new repo actually *need* default template content?' \ /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
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).