From: Sebastian Gniazdowski <psprint@zdharma.org>
To: git@vger.kernel.org
Subject: There should be a `.gitbless; file, protecting files from git clean
Date: Mon, 28 Jan 2019 03:41:39 +0100 [thread overview]
Message-ID: <etPan.5c4e6be4.2ca84d68.4d5@zdharma.org> (raw)
Hello,
Keepiing repo clean with `git clean -dxf' is a very pleasant experience. However, ability to use it ends when one gets untracked but *wanted* files in the repo, like an untracked TODO.
Could a .gitbless file be a solution? I would list in it, e.g.:
TODO
and this way be able to use `git -dxf' again. What do you think?
--
Sebastian Gniazdowski
News: https://twitter.com/ZdharmaI
IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin
Blog: http://zdharma.org
next reply other threads:[~2019-01-28 2:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 2:41 Sebastian Gniazdowski [this message]
2019-01-28 5:05 ` There should be a `.gitbless; file, protecting files from git clean Duy Nguyen
2019-01-28 5:24 ` Sebastian Gniazdowski
2019-01-29 0:48 ` Duy Nguyen
2019-01-28 6:23 ` Sebastian Gniazdowski
2019-01-28 15:30 ` Sebastian Gniazdowski
2019-01-29 1:00 ` Duy Nguyen
2019-01-28 18:08 ` Junio C Hamano
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=etPan.5c4e6be4.2ca84d68.4d5@zdharma.org \
--to=psprint@zdharma.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox