From: Jeff King <peff@peff.net>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: .gitignore polution
Date: Sun, 15 Nov 2009 04:43:53 -0500 [thread overview]
Message-ID: <20091115094352.GA21477@coredump.intra.peff.net> (raw)
In-Reply-To: <fabb9a1e0911141557k5f6b0b8aud48b95784a9da4e3@mail.gmail.com>
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
next prev parent reply other threads:[~2009-11-15 9:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-14 23:57 .gitignore polution Sverre Rabbelier
2009-11-15 9:43 ` Jeff King [this message]
2009-11-16 0:22 ` Sverre Rabbelier
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=20091115094352.GA21477@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=srabbelier@gmail.com \
/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).