From: Michal Marek <mmarek@suse.cz>
To: Gabriel de Perthuis <g2p.code@gmail.com>
Cc: linux-kbuild@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] scripts: Don't run find across mountpoints
Date: Sun, 23 Jun 2013 23:31:39 +0200 [thread overview]
Message-ID: <51C7693B.2050504@suse.cz> (raw)
In-Reply-To: <51B5F083.1050203@gmail.com>
Hi Gabriel,
sorry for the late feedback.
Dne 10.6.2013 17:28, Gabriel de Perthuis napsal(a):
> Use RCS_FIND_IGNORE in more places.
Can you split it into two parts - one adding the missing RCS_FIND_IGNORE
to some find invocations, and other adding the -xdev option? While the
first change is obvious, I am in two minds abount the -xdev change. Your
original problem was .git in a separate filesystem, which is dealt with
by RCS_FIND_IGNORE. The actual source tree should reside in a single
filesystem in any sane setup. OTOH, if somebody really wishes to have
part of the source tree under a separate mountpoint, he probably has a
good reason for this.
Thanks,
Michal
prev parent reply other threads:[~2013-06-23 21:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 15:28 [PATCH] scripts: Don't run find across mountpoints Gabriel de Perthuis
2013-06-23 21:31 ` Michal Marek [this message]
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=51C7693B.2050504@suse.cz \
--to=mmarek@suse.cz \
--cc=g2p.code@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--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 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.