Git's own .gitignore files should only contain things created by Git's build systems, not editor-specific droppings. See the discussion following the "[PATCH] Add git format-patch produced patches to .gitignore" thread (<1273958566-7328-1-git-send-email-avarab@xxxxxxxxx>). --- On Mon, May 17, 2010 at 01:35, Jonathan Nieder <jrnieder@xxxxxxxxx> wrote: > Michael J Gruber wrote: > >> Does the git build process call format-patch? No! The .gitignore we >> distribute is meant for things the build process creates > > Ah, true. I seem to remember a thread long ago about whether to > include editor droppings in .gitignore, but I canâ??t find it in > the git or lkml archive. > > gitâ??s .gitignore does not include .*.swp, \#*#, *~, indeed. Thanks both of you, I stand corrected. Anyway, I guess this is a bug then. It's the only thing ignored by Git's various .gitignore files that isn't created by the build system. git-gui/po/.gitignore | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/git-gui/po/.gitignore b/git-gui/po/.gitignore index a89cf44..e358dd1 100644 --- a/git-gui/po/.gitignore +++ b/git-gui/po/.gitignore @@ -1,2 +1 @@ *.msg -*~ -- 1.7.1.84.gd92f8 -- 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