From: Oleg Taranenko <olegtaranenko@gmail.com>
To: Junio C Hamano <gitster@pobox.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: Thu, 6 Mar 2025 01:04:21 +0100 [thread overview]
Message-ID: <CABEd3j9WqykwmNF_z-eeKcdFRAjYpKkFnciVBwpYLnteS62yZA@mail.gmail.com> (raw)
In-Reply-To: <xmqqsenrjaka.fsf@gitster.g>
On Thu, 6 Mar 2025 at 00:56, Junio C Hamano <gitster@pobox.com> wrote:
> I was referring to .git/info because of the .git/info/excludes file.
.git/info/excludes is a great feature, but it often needs to persist
ignored structure, for example, in case of creating a zillion small
projects/repos for the learning process.
prev parent reply other threads:[~2025-03-06 0:04 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
2025-03-06 0:04 ` Oleg Taranenko [this message]
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=CABEd3j9WqykwmNF_z-eeKcdFRAjYpKkFnciVBwpYLnteS62yZA@mail.gmail.com \
--to=olegtaranenko@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 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 NNTP newsgroup(s).