public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan III Sobieski <jan3sobi3ski@gmail.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] add random binaries to .gitignore
Date: Sun, 28 Mar 2010 16:02:54 +0200	[thread overview]
Message-ID: <4BAF618E.2010604@gmail.com> (raw)
In-Reply-To: <20100328141957.GA3689@core2>

W dniu 2010-03-28 16:19, Alexey Dobriyan pisze:
> On Sun, Mar 28, 2010 at 03:38:31PM +0200, Jan III Sobieski wrote:
>> W dniu 2010-03-28 15:35, Alexey Dobriyan pisze:
>>> On Sun, Mar 28, 2010 at 02:38:07PM +0200, Jan III Sobieski wrote:
>>>> +# random binary files
>>>> +Documentation/filesystems/dnotify_test
>>>> +Documentation/laptops/dslm
>>>> +Documentation/timers/hpet_example
>>>> +Documentation/vm/hugepage-mmap
>>>> +Documentation/vm/hugepage-shm
>>>> +Documentation/vm/map_hugetlb
>>>> +arch/x86/boot/compressed/vmlinux
>>>> +arch/x86/tools/test_get_len
>>>
>>> This should go to per-directory gitiignores.
>>
>> I agree that it is not the best solution. But one directory one
>> .gitignore also isn't the best, so I propose this
> 
> .gitignore in leaf directory is the status quo.
> 
> 	find . -type f -name '\.gitignore'

Ok

-- 
Jan III Sobieski

Signed-off-by: Jan III Sobieski <jan3sobi3ski@gmail.com>

diff --git a/Documentation/filesystems/.gitignore
b/Documentation/filesystems/.gitignore
new file mode 100644
index 0000000..1ddd62a
--- /dev/null
+++ b/Documentation/filesystems/.gitignore
@@ -0,0 +1,2 @@
+dnotify_test
+
diff --git a/Documentation/laptops/.gitignore
b/Documentation/laptops/.gitignore
new file mode 100644
index 0000000..f6bb9d0
--- /dev/null
+++ b/Documentation/laptops/.gitignore
@@ -0,0 +1,2 @@
+dslm
+
diff --git a/Documentation/timers/.gitignore
b/Documentation/timers/.gitignore
new file mode 100644
index 0000000..f710cba
--- /dev/null
+++ b/Documentation/timers/.gitignore
@@ -0,0 +1,2 @@
+hpet_example
+
diff --git a/Documentation/vm/.gitignore b/Documentation/vm/.gitignore
index 09b164a..3c65a46 100644
--- a/Documentation/vm/.gitignore
+++ b/Documentation/vm/.gitignore
@@ -1,2 +1,6 @@
 page-types
 slabinfo
+hugepage-mmap
+hugepage-shm
+map_hugetlb
+
diff --git a/arch/x86/boot/compressed/.gitignore
b/arch/x86/boot/compressed/.gitignore
index 4a46fab..b71c8ca 100644
--- a/arch/x86/boot/compressed/.gitignore
+++ b/arch/x86/boot/compressed/.gitignore
@@ -1,4 +1,5 @@
 relocs
+vmlinux
 vmlinux.bin.all
 vmlinux.relocs
 vmlinux.lds
diff --git a/arch/x86/tools/.gitignore b/arch/x86/tools/.gitignore
new file mode 100644
index 0000000..b1ac2dc
--- /dev/null
+++ b/arch/x86/tools/.gitignore
@@ -0,0 +1,2 @@
+test_get_len
+

  reply	other threads:[~2010-03-28 14:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-28 12:38 [PATCH] add random binaries to .gitignore Jan III Sobieski
2010-03-28 13:35 ` Alexey Dobriyan
2010-03-28 13:38   ` Jan III Sobieski
2010-03-28 14:19     ` Alexey Dobriyan
2010-03-28 14:02       ` Jan III Sobieski [this message]
2010-04-07  4:11         ` Jan III Sobieski
2010-04-07  4:24           ` Amerigo Wang
2010-04-08  9:36             ` Michal Marek

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=4BAF618E.2010604@gmail.com \
    --to=jan3sobi3ski@gmail.com \
    --cc=adobriyan@gmail.com \
    --cc=linux-kernel@vger.kernel.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