From: "William Hubbs" <williamh@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/catalyst:catalyst_2 commit in: /, files/, doc/
Date: Sat, 25 Jun 2011 19:54:04 +0000 (UTC) [thread overview]
Message-ID: <f0d4cca11d01c96dab41ad58a15f067efe4d7084.WilliamH@gentoo> (raw)
commit: f0d4cca11d01c96dab41ad58a15f067efe4d7084
Author: William Hubbs <w.d.hubbs <AT> gmail <DOT> com>
AuthorDate: Sat Jun 25 18:28:45 2011 +0000
Commit: William Hubbs <williamh <AT> gentoo <DOT> org>
CommitDate: Sat Jun 25 19:53:18 2011 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/catalyst.git;a=commit;h=f0d4cca1
fix ignore patterns
The top level .gitignore file should contain things you want ignored
through the entire tree. Specific files you want ignored should go in
.gitignore files in their respective directories unless they appear more
than once in the tree.
---
.gitignore | 3 ---
doc/.gitignore | 2 ++
files/.gitignore | 1 +
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/.gitignore b/.gitignore
index 9de5788..539da74 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,4 +1 @@
*.py[co]
-/files/catalyst.1
-/doc/subarches.generated.txt
-/doc/subarches.generated.xml
diff --git a/doc/.gitignore b/doc/.gitignore
new file mode 100644
index 0000000..b998e26
--- /dev/null
+++ b/doc/.gitignore
@@ -0,0 +1,2 @@
+subarches.generated.txt
+subarches.generated.xml
diff --git a/files/.gitignore b/files/.gitignore
new file mode 100644
index 0000000..10acc02
--- /dev/null
+++ b/files/.gitignore
@@ -0,0 +1 @@
+catalyst.1
next reply other threads:[~2011-06-25 19:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-25 19:54 William Hubbs [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-24 17:13 [gentoo-commits] proj/catalyst:catalyst_2 commit in: /, files/, doc/ Sebastian Pipping
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=f0d4cca11d01c96dab41ad58a15f067efe4d7084.WilliamH@gentoo \
--to=williamh@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox