On Monday 2007 October 01, martin f krafft wrote: > 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. But it _is_ a conflict. Conflicts have to be resolved. I'm having difficulty understanding what you think git should be doing in these cases? > (and yes, this is basically a reincarnation of my case for > .gitignore.d [http://lists.zerezo.com/git/msg627581.html]). I don't see that that would help. All you are doing with a gitignore.d is swapping lines for files, the conflicts would still exist. Presumably you are hoping that the separate branches will make different files in gitignore.d and hence can't conflict; but then you've just pushed the conflict to a place where it won't be seen (and also made a terrible mess of the merged branch gitignore.d). branchA:.gitignore.d/branchAignores branchB:.gitignore.d/branchBignores Over time you would get: master:.gitignore.d/branchAignores master:.gitignore.d/branchBignores master:.gitignore.d/branchCignores master:.gitignore.d/branchDignores master:.gitignore.d/branchEignores master:.gitignore.d/branchFignores Then, assuming the conflicts you get now occur for a reason, you will get conflicts within the .gitignore.d/ directory. Let's say branchCignores adds *.o and branchFignores removes *.o from the ignores. Who is right? Who knows, and worse than that you didn't see the conflict when it happened so it wasn't resolved and the master branch was left with conflicts in it. Of course the conflicts in that case aren't in the form of "<<<<<" markers, but they are no less conflicts just because they're invisible. Eventually someone is going to want to combine this ever-increasing set of ignore files into one. i.e. they'll merge them. In which case why couldn't you do the merge at the correct time - when the branch was merged? Andy -- Dr Andy Parkins, M Eng (hons), MIET andyparkins@xxxxxxxxx - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
