From: Louis Strous <louis.strous@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH/RFC v4 0/2] Add -e/--exclude to git clean.
Date: Thu, 23 Sep 2010 09:05:05 +0000 (UTC) [thread overview]
Message-ID: <loom.20100923T103502-148@post.gmane.org> (raw)
In-Reply-To: 20100720191131.GA2688@localhost.localdomain
The git clean -e option is more useful than just for stuff that you plan to
bring under git control later. It also allows to retain per-user configurations
of external tools when using git clean to remove all build results and
intermediate files. This leads to the enhancement request described below.
Most IDEs (integrated development environments) allow the user to configure
various display and debugger options, and store those options in some
configuration file. Such user option files should not be under git control in a
multi-user environment, because then all users are forced to use the same
options. Yet these user option files should not be deleted when the rest of the
untracked files are deleted (through git clean), otherwise the user options are
lost.
git clean -x -d -f -e "pattern" removes all untracked files except those
matching the pattern. However, it is cumbersome to specify these patterns every
time. It would be more convenient if git clean would read such patterns from a
file similar to .gitignore (maybe .gitignoreclean?). Then that file itself
could be put under git control and shared with the other developers.
I request implementation of this feature.
Best regards,
Louis Strous
prev parent reply other threads:[~2010-09-23 9:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-19 15:50 [PATCH] Add --exclude to git-clean.j Jared Hance
2010-07-19 16:14 ` Jonathan Nieder
2010-07-19 16:21 ` Jared Hance
2010-07-19 16:18 ` [PATCH v2] Add --exclude to git-clean Jared Hance
2010-07-19 17:43 ` Junio C Hamano
2010-07-19 18:22 ` Jared Hance
2010-07-19 18:39 ` [PATCH v3] " Jared Hance
2010-07-20 16:28 ` [PATCH/RFC v4 0/2] Add -e/--exclude to git clean Jared Hance
2010-07-20 16:29 ` [PATCH/RFC v4 1/2] Add --exclude to git-clean Jared Hance
2010-07-20 16:30 ` [PATCH 2/2] Add test for git clean -e Jared Hance
2010-07-20 17:03 ` [PATCH/RFC v4 0/2] Add -e/--exclude to git clean Aaron Crane
2010-07-20 17:13 ` Jared Hance
2010-07-20 18:02 ` Junio C Hamano
2010-07-20 18:23 ` Junio C Hamano
2010-07-20 19:11 ` Jared Hance
2010-09-23 9:05 ` Louis Strous [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=loom.20100923T103502-148@post.gmane.org \
--to=louis.strous@gmail.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 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).