From: Junio C Hamano <gitster@pobox.com>
To: Oleg Taranenko <olegtaranenko@gmail.com>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>,
Tech Kenya <techkenya@protonmail.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Suggestion: Enhance git init with Language-Specific Templates
Date: Wed, 05 Mar 2025 15:56:53 -0800 [thread overview]
Message-ID: <xmqqsenrjaka.fsf@gitster.g> (raw)
In-Reply-To: <CABEd3j-36C_LUOetg0qLofrby9M1Hixkh4o7sQkkyyWuTqHQvQ@mail.gmail.com> (Oleg Taranenko's message of "Thu, 6 Mar 2025 00:53:30 +0100")
Oleg Taranenko <olegtaranenko@gmail.com> writes:
> On Wed, 5 Mar 2025 at 23:53, Junio C Hamano <gitster@pobox.com> wrote:
>
>> I wouldn't have thrown objects in the --template directory, and I
>> wouldn't count on things outside what the mechanism was invented for
>> (namely, .git/hooks and possibly .git/info/ files) would forever be
>> copied in newer versions of Git, but certainly "git init --template"
>> mechanism sounds like a good escape hatch than mucking with Git code
>> base to teach it myriad of languages and their dialects.
>
> It sounds like creating a copy of the .gitignore structure requires
> the user to learn bash script syntax. :-D I'd like to suggest adding
> one more option to the init --template <template/dir>
> --only-gitignores. It will not deal with all the complicated mechanics
> behind hooks/etc, and will only look at the template folder structure
> and copy **/.gitignore into the newly created worktree. In case of
> existing .gitignore files, just put warnings and do not override
> those.
I was referring to .git/info because of the .git/info/excludes file.
next prev parent reply other threads:[~2025-03-05 23:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 11:49 Suggestion: Enhance git init with Language-Specific Templates Tech Kenya
2025-03-05 22:43 ` brian m. carlson
2025-03-05 22:50 ` rsbecker
2025-03-05 22:52 ` Junio C Hamano
2025-03-05 23:53 ` Oleg Taranenko
2025-03-05 23:56 ` Junio C Hamano [this message]
2025-03-06 0:04 ` Oleg Taranenko
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=xmqqsenrjaka.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=olegtaranenko@gmail.com \
--cc=sandals@crustytoothpaste.net \
--cc=techkenya@protonmail.com \
/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.