git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] Remove editor-specific droppings from .gitignore

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
May 17, 2010, 02:04 UTC
Message-ID
<1274061883-18043-1-git-send-email-avarab@gmail.com>
In-Reply-To
<20100517013549.GA19081@progeny.tock>

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@gmail.com>). ---

On Mon, May 17, 2010 at 01:35, Jonathan Nieder <jrnieder@gmail.com> wrote:
Show 10 quoted lines
> 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
Previous: Jonathan NiederNext: Jonathan Nieder
Message 7 of 9 in “Add git format-patch produced patches to .gitignore”
  1. Add git format-patch produced patches to .gitignoreÆvar Arnfjörð Bjarmason, May 15, 2010
  2. Pavan Kumar SunkaraMay 16, 2010
  3. Jonathan NiederMay 16, 2010
  4. Ævar Arnfjörð BjarmasonMay 16, 2010
  5. Michael J GruberMay 16, 2010
  6. Jonathan NiederMay 17, 2010
  7. Remove editor-specific droppings from .gitignoreÆvar Arnfjörð Bjarmason, May 17, 2010
  8. Jonathan NiederMay 17, 2010
  9. Michael J GruberMay 17, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.