merging .gitignore

From: martin f krafft <madduck@madduck.net>
Date: Oct 1, 2007, 13:03 UTC
Message-ID: <20071001130314.GA5932@lapse.madduck.net>

Dear gits (oh dear…),

we just ran into a problem in a git-managed project and I'd be interested to learn how you approach this.

Our main line ("upstream"), which tracks a remote repository, does not have a .gitignore file. For new features, we use feature branches, and we merge those into an integration branch ("master") and track them separately of upstream.

Feature branch A has a .gitignore file, and it's been merged into master for a while. Today, feature branch B failed to merge into master because it also provides a .gitignore file. We can obviously resolve the conflict, but I wonder whether there is a better way to deal with this since we deal with quite a large number of new feature branches and it's only a matter of time until the next one will conflict because of .gitignore.

(and yes, this is basically a reincarnation of my case for .gitignore.d [http://lists.zerezo.com/git/msg627581.html]).

Thoughts,

-- 
martin;              (greetings from the heart of the sun.)
  \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
 
kermit: why are there so many songs about rainbows?
fozzy: that's part of what rainbows do.
 
spamtraps: madduck.bogus@madduck.net