From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: git@vger.kernel.org
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: [PATCH] Remove editor-specific droppings from .gitignore
Date: Mon, 17 May 2010 02:04:43 +0000 [thread overview]
Message-ID: <1274061883-18043-1-git-send-email-avarab@gmail.com> (raw)
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:
> 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
next prev parent reply other threads:[~2010-05-17 2:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-15 21:22 [PATCH] Add git format-patch produced patches to .gitignore Ævar Arnfjörð Bjarmason
2010-05-16 6:27 ` Pavan Kumar Sunkara
2010-05-16 7:52 ` Jonathan Nieder
2010-05-16 13:06 ` Ævar Arnfjörð Bjarmason
2010-05-16 14:05 ` Michael J Gruber
2010-05-17 1:35 ` Jonathan Nieder
2010-05-17 2:04 ` Ævar Arnfjörð Bjarmason [this message]
2010-05-17 2:22 ` Jonathan Nieder
2010-05-17 7:52 ` Michael J Gruber
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=1274061883-18043-1-git-send-email-avarab@gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.