.gitignore polution

.gitignore polution

[Sverre Rabbelier]

Heya,

I usually compile git from next (sometimes pu to test out a new
feature), and when I then switch back to a development branch (usually
based off master) I get something like this:

$ git status
# On branch remote-helpers
# Untracked files:
#   (use "git add <file>..." to include in what will be committed)
#
#	git-http-backend
#	git-notes
#	git-remote-hg
#	test-index-version

Now I can easily do 'git clean -f', but it's somewhat annoying. How do
other developers deal with this?

-- 
Cheers,

Sverre Rabbelier

Re: .gitignore polution

[Jeff King]

On Sun, Nov 15, 2009 at 12:57:31AM +0100, Sverre Rabbelier wrote:

> I usually compile git from next (sometimes pu to test out a new
> feature), and when I then switch back to a development branch (usually
> based off master) I get something like this:
> 
> $ git status
> # On branch remote-helpers
> # Untracked files:
> #   (use "git add <file>..." to include in what will be committed)
> #
> #	git-http-backend
> #	git-notes
> #	git-remote-hg
> #	test-index-version
> 
> Now I can easily do 'git clean -f', but it's somewhat annoying. How do
> other developers deal with this?

I use "git clean". :)

The other option is to mark them for ignore outside of the
branch-specific ignore:

  git ls-files -o --exclude-standard >>.git/info/exclude

-Peff

Re: .gitignore polution

[Sverre Rabbelier]

Heya,

On Sun, Nov 15, 2009 at 10:43, Jeff King <peff@peff.net> wrote:
> The other option is to mark them for ignore outside of the
> branch-specific ignore:
>
>  git ls-files -o --exclude-standard >>.git/info/exclude

Ah, that would work, thanks! :)

-- 
Cheers,

Sverre Rabbelier