From: Santiago Torres <firstname.lastname@example.org>
To: Jeff King <email@example.com>
Cc: "Ævar Arnfjörð Bjarmason" <firstname.lastname@example.org>,
"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 10:38:25 -0400 [thread overview]
Message-ID: <20180601143823.h7fvri25q7om4whn@LykOS.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 1390 bytes --]
On Fri, Jun 01, 2018 at 03:06:10AM -0400, Jeff King wrote:
> 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).
+1. It'd probably be worth having the sample hooks be part of the
installation, but not as part of every repository (e.g., hold them under
/usr/share/git/samples/hooks/ or something along those lines).
> I also wish hooks were just shell snippets in the config files that
> could follow the usual config-precedence rules.
I like this idea, but I'd probably keep the snippets in a separate file
to keep things clean.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-06-01 14:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 13:00 does a new repo actually *need* default template content? Robert P. J. Day
2018-05-28 17:56 ` Ævar Arnfjörð Bjarmason
2018-06-01 7:06 ` Jeff King
2018-06-01 14:38 ` Santiago Torres [this message]
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).