From: Pavel Roskin <proski@gnu•org>
To: Alex Riesen <raa.lkml@gmail•com>
Cc: Martin Waitz <tali@admingilde•org>, git@vger•kernel.org
Subject: Re: [PATCH] Add git-clean command
Date: Tue, 04 Apr 2006 11:32:29 -0400 [thread overview]
Message-ID: <1144164749.30675.12.camel@dv> (raw)
In-Reply-To: <81b0412b0604040217s3b8863d3w1b79400c42ca2b90@mail.gmail.com>
On Tue, 2006-04-04 at 11:17 +0200, Alex Riesen wrote:
> On 4/4/06, Martin Waitz <tali@admingilde•org> wrote:
> > What is the use case of cleaning up all untracked files without also
> > cleaning ignored files?
>
> Thinks of git's .gitignore: it has config.mak in it. Are you sure you want
> "clean" your build customizations?
In may case, I normally want to remove copies of the sources. For
example, I take foo.c, make a clean copy of it, then I change and test
it. If if doesn't work and I want to try another approach, I copy it to
foo.c-bad or foo.c-approach1. I also make diffs between files to see
what exactly I changed. I may also create files for output, valgrind
logs and so on.
At some point, I'm satisfied with foo.c, so I commit it. Then I want to
remove copies, diffs and other stuff. Yet I don't want to rebuild
everything.
It's very rare that I add a new file, and I always remember to add it to
the version control. But I'll consider adding an option to only remove
ignored files.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2006-04-04 15:32 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
2006-04-04 9:08 ` Junio C Hamano
2006-04-04 9:17 ` Alex Riesen
2006-04-04 15:32 ` Pavel Roskin [this message]
-- 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=1144164749.30675.12.camel@dv \
--to=proski@gnu$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=raa.lkml@gmail$(echo .)com \
--cc=tali@admingilde$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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