From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: dwheeler@dwheeler.com, git <git@vger.kernel.org>
Subject: Re: [PATCH] clone: Warn if clone lacks LICENSE or COPYING file
Date: Fri, 03 Apr 2015 14:26:34 -0700 [thread overview]
Message-ID: <xmqqtwwwgayd.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CACBZZX67igE67+y7Tme=_OC7JiT726qB4X18+8Mvg1ewssQ_ug@mail.gmail.com> ("Ævar Arnfjörð Bjarmason"'s message of "Sun, 22 Mar 2015 18:56:52 +0100")
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
> As others have indicated here this feature is really specific to a
> single lint-like use-case and doesn't belong in clone as a built-in
> feature.
>
> However perhaps an interesting generalization of this would be
> something like a post-clone hook, obviously you couldn't store that in
> .git/hooks/ like other githooks(5) since there's no repo yet,
Yes, and these things come from templates, and you can specify the
template source location when running "git clone".
So I do not think anything is needed on our side and it's all doable
with what the users already have, as long as we are talking about
making it only an opt-in feature.
Which means
> You could also just have a shell alias that wrapped git-clone...
is also perfectly acceptable, I would think.
next prev parent reply other threads:[~2015-04-03 21:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-21 18:06 [PATCH] clone: Warn if clone lacks LICENSE or COPYING file David A. Wheeler
2015-03-21 20:21 ` Dennis Kaarsemaker
2015-03-22 4:20 ` Stefan Beller
2015-03-22 4:59 ` Junio C Hamano
2015-03-23 16:46 ` David A. Wheeler
2015-03-23 21:00 ` Ævar Arnfjörð Bjarmason
2015-03-22 17:56 ` Ævar Arnfjörð Bjarmason
2015-04-03 21:18 ` David A. Wheeler
2015-04-03 21:26 ` Junio C Hamano [this message]
2015-03-26 16:56 ` Kevin D
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=xmqqtwwwgayd.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=dwheeler@dwheeler.com \
--cc=git@vger.kernel.org \
/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.