Re: does a new repo actually *need* default template content?
- From
Jeff King <peff@peff.net>
- Date
- Jun 1, 2018, 07:06 UTC
- Message-ID
- <20180601070609.GC15578@sigill.intra.peff.net>
- In-Reply-To
- <87h8mr7jgj.fsf@evledraar.gmail.com>
On Mon, May 28, 2018 at 07:56:12PM +0200, Ævar Arnfjörð Bjarmason wrote:
Show 16 quoted lines
>
> 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