Ævar Arnfjörð Bjarmason <ava...@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. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
