From: Martin Waitz <tali@admingilde.org>
To: Pavel Roskin <proski@gnu.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Add git-clean command
Date: Tue, 4 Apr 2006 10:20:02 +0200 [thread overview]
Message-ID: <20060404082002.GJ4663@admingilde.org> (raw)
In-Reply-To: <20060403221841.25097.18242.stgit@dv.roinet.com>
[-- Attachment #1: Type: text/plain, Size: 597 bytes --]
hoi :)
> +-x::
> + Don't use the ignore rules. This allows removing all untracked
> + files, including build products. This can be used (possibly in
> + conjunction with gitlink:git-reset[1]) to create a pristine
> + working directory to test a clean build.
as ignored files are generally generated files, doesn't it make sense
to clean up the "ignored" files, and leave other untracked files
alone? That way you don't loose files which you forgot to add to git.
What is the use case of cleaning up all untracked files without also
cleaning ignored files?
--
Martin Waitz
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-04-04 8:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 22:18 [PATCH] Add git-clean command Pavel Roskin
2006-04-04 0:06 ` Junio C Hamano
2006-04-04 10:58 ` Sam Ravnborg
2006-04-04 15:52 ` Pavel Roskin
2006-04-05 16:02 ` unchecked uses of strdup Jim Meyering
2006-04-06 14:11 ` Alex Riesen
2006-04-05 6:00 ` [PATCH] Add git-clean command Pavel Roskin
2006-04-04 8:20 ` Martin Waitz [this message]
2006-04-04 9:08 ` Junio C Hamano
2006-04-04 9:17 ` Alex Riesen
2006-04-04 15:32 ` Pavel Roskin
-- strict thread matches above, loose matches on Subject: below --
2006-04-05 6:00 Pavel Roskin
2006-04-05 6:25 ` Jakub Narebski
2006-04-03 21:59 Pavel Roskin
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=20060404082002.GJ4663@admingilde.org \
--to=tali@admingilde.org \
--cc=git@vger.kernel.org \
--cc=proski@gnu.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 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.