public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Gabriel de Perthuis <g2p.code@gmail.com>
To: Michal Marek <mmarek@suse.cz>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] deb-pkg: Don't run find across mountpoints
Date: Mon, 10 Jun 2013 16:19:18 +0200	[thread overview]
Message-ID: <51B5E066.2010009@gmail.com> (raw)
In-Reply-To: <51B5D336.3070405@suse.cz>

Le 10/06/2013 15:23, Michal Marek a écrit :
> On 10.6.2013 15:20, Gabriel de Perthuis wrote:
>> Le 10/06/2013 15:15, Gabriel de Perthuis a écrit :
>>> Le lun. 10 juin 2013 15:07:56 CEST, Michal Marek a écrit :
>>>> What kind of mountpoint zoo do you maintain in your build tree? :) We
>>>> run a find in make clean, make mrproper and other targets. So you might
>>>> need to fix more places. But please explain your use case.
>>>
>>> I happened to be running a fuse thing (git fs, mounted under .git/fs);
>>> recursing that can take a *long* time.
>>>
>>> `find .` is the only one that actually runs into trouble, although it
>>> might be good if -xdev could be the default (through a shell
>>> function maybe?).
> 
> So make deb-pkg saves the md5sums of all files under .git?? Then the
> right fix would be to export RCS_FIND_IGNORE and use it in the builddeb
> script.

Sounds like a good idea.  It doesn't work as is because the backslashes
in \( seem to be delayed by make and can't be used as is, removing the
backslashes doesn't work either, and it takes a long time to test.


      reply	other threads:[~2013-06-10 14:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-09 16:14 [PATCH] deb-pkg: Don't run find across mountpoints Gabriel de Perthuis
2013-06-10 13:07 ` Michal Marek
2013-06-10 13:15   ` Gabriel de Perthuis
2013-06-10 13:20     ` Gabriel de Perthuis
2013-06-10 13:23       ` Michal Marek
2013-06-10 14:19         ` Gabriel de Perthuis [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=51B5E066.2010009@gmail.com \
    --to=g2p.code@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=mmarek@suse.cz \
    /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