threads / discuss / 21623

.gitignore polution

Subject: .gitignore polution

## tl;dr

3 messages between Nov 14, 2009 and Nov 16, 2009.

replies: 2people: 2as markdown or json

Sverre Rabbelier· Nov 14, 2009, 23:57 UTC · lore

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

Jeff King· Nov 15, 2009, 09:43 UTC · re: Sverre Rabbelier · lore

Re: .gitignore polution

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

Show 16 quoted lines

> 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

Sverre Rabbelier· Nov 16, 2009, 00:22 UTC · re: Jeff King · lore

Re: .gitignore polution

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