<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.gnu.findutils.patches">
    <title>gmane.comp.gnu.findutils.patches</title>
    <link>http://blog.gmane.org/gmane.comp.gnu.findutils.patches</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnu.findutils.patches/511"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnu.findutils.patches/503"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnu.findutils.patches/501"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnu.findutils.patches/474"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnu.findutils.patches/457"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnu.findutils.patches/382"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnu.findutils.patches/372"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnu.findutils.patches/348"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnu.findutils.patches/320"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnu.findutils.patches/319"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnu.findutils.patches/511">
    <title>[PATCH] updatedb: add further entries toPRUNEFS defaults</title>
    <link>http://comments.gmane.org/gmane.comp.gnu.findutils.patches/511</link>
    <description>&lt;pre&gt;From f18c966940c7769f4be1acea5567430ee290158c Mon Sep 17 00:00:00 2001
From: Bernhard Voelker &amp;lt;mail&amp;lt; at &amp;gt;bernhard-voelker.de&amp;gt;
Date: Wed, 5 Dec 2012 12:09:41 +0100
Subject: [PATCH] updatedb: add further entries to PRUNEFS defaults

Merge new entries from OpenSuSE project, e.g. there were hangs
on nfs4 mounts.

* locate/updatedb.sh (PRUNEFS): Add 9P, cifs, nfs4, and unknown.
Sort entries alphabetically.
---
 locate/updatedb.sh |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/locate/updatedb.sh b/locate/updatedb.sh
index a9ded7b..cb3f39a 100644
--- a/locate/updatedb.sh
+++ b/locate/updatedb.sh
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -246,7 +246,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; do
 done


-: ${PRUNEFS="nfs NFS proc afs smbfs autofs iso9660 ncpfs coda devpts ftpfs devfs mfs sysfs shfs"}
+: ${PRUNEFS="9P NFS afs autofs cifs coda devfs devpts ftpfs iso9660 mfs ncpfs nfs nfs4 proc shfs smbfs sysfs unknown"}

 if test -n "$PRUNEFS"; then
 prunefs_exp=`echo $PRUNEFS |sed -e 's/\([^ ][^ ]*\)/-o -fstype \1/g' \
&lt;/pre&gt;</description>
    <dc:creator>Bernhard Voelker</dc:creator>
    <dc:date>2012-12-05T11:16:05</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnu.findutils.patches/503">
    <title>[PATCH] fix comment/changelog typos</title>
    <link>http://comments.gmane.org/gmane.comp.gnu.findutils.patches/503</link>
    <description>&lt;pre&gt;
Here's a patch to fix some typos.

I made this change manually, because the tool proposed three
alternatives:

diff --git a/m4/nullsort.m4 b/m4/nullsort.m4
index 5f592f7..10a1a93 100644
--- a/m4/nullsort.m4
+++ b/m4/nullsort.m4
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -13,7 +13,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; else
         # sort thinks there is more than one input line there.   We have
         # to make sort -c do its thing with the input lines in the wrong
         # order to determine that (we can't do it in one shot because
-        # if sort returns nonzero we cant tell that it wasn't just
+        # if sort returns nonzero we can't tell that it wasn't just
         # complaining about this unknown -z option.
         if $SORT -z -c &amp;lt; "${srcdir:-.}/m4/order-bad.bin" 2&amp;gt;/dev/null &amp;gt;/dev/null
         then

Then noticed "dum" being changed to "dumb", but only in two
exception lists.  There, just removing the non-word is better.

Finally, using http://github.com/lyda/misspell-check and
some perl to massage its diagnostics into sed commands:

git ls-files|grep -v '\.po$'&lt;/pre&gt;</description>
    <dc:creator>Jim Meyering</dc:creator>
    <dc:date>2012-06-04T11:29:24</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnu.findutils.patches/501">
    <title>find.texi: uk and other consistency</title>
    <link>http://comments.gmane.org/gmane.comp.gnu.findutils.patches/501</link>
    <description>&lt;pre&gt;Hi James,

I'm not sure it's really viable to try to write Texinfo in UK English
(there's a hyphenation problem at least, without running TeX in some
special way), but since evidently find.texi is mostly written that way
now, here is a small patch to make things a little more consistent.
(I don't doubt plenty of infelicities remain, this is just what I
noticed in a quick look.)

Not included in this patch: all those &amp;lt; at &amp;gt;subsections that don't have
corresponding should really be &amp;lt; at &amp;gt;subheadings.  Or, probably better, they
should get nodes, since now the nodes end up being hundreds of lines
long.

Sorry I can't easily deal with git and give you the patch that way,
hope this is ok.

Thanks,
k

 Karl Berry  &amp;lt;karl&amp;lt; at &amp;gt;gnu.org&amp;gt;
* find.texi (&amp;lt; at &amp;gt;copying): add 2011, period outside quotes.
(thoughout): use UK spelling and " -- " convention.
(section names): use &amp;lt; at &amp;gt;code where needed.

--- ORIG/find.texi2011-12-29 11:09:38.000000000 -0800
+++ find.texi2011-12-29 11:23:41.000000000 -0800
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -33,4 +33,4 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
 
-Copyright (C) 1994, 1996&lt;/pre&gt;</description>
    <dc:creator>Karl Berry</dc:creator>
    <dc:date>2011-12-29T21:56:15</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnu.findutils.patches/474">
    <title>[PATCH 1/9] File system type names should beuntranslated strings.</title>
    <link>http://comments.gmane.org/gmane.comp.gnu.findutils.patches/474</link>
    <description>&lt;pre&gt;* find/fstype.c (file_system_type_uncached): When the file system
type is not known, return the literal string "unknown", instead of
a translation of that.  This allows a find command line like "find
. -fstype unknown" to work in a variety of locales, instead of
just the C locale.  Similarly, for the AFS file system, always
return "afs".
* NEWS: Mention this change.
---
 ChangeLog     |   11 +++++++++++
 NEWS          |    7 +++++++
 find/fstype.c |    4 ++--
 3 files changed, 20 insertions(+), 2 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 412d219..581de09 100644
--- a/ChangeLog
+++ b/ChangeLog
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -1,3 +1,14 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
+2011-07-09  James Youngman  &amp;lt;jay&amp;lt; at &amp;gt;gnu.org&amp;gt;
+
+File system type names should be untranslated strings.
+* find/fstype.c (file_system_type_uncached): When the file system
+type is not known, return the literal string "unknown", instead of
+a translation of that.  This allows a find command line like "find
+. -fstype unknown" to work in a variety of locales, instead of
+just the C locale.&lt;/pre&gt;</description>
    <dc:creator>James Youngman</dc:creator>
    <dc:date>2011-07-09T22:15:43</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnu.findutils.patches/457">
    <title>[PATCH 1/7] Clarify variable naming ininsert_fprintf.</title>
    <link>http://comments.gmane.org/gmane.comp.gnu.findutils.patches/457</link>
    <description>&lt;pre&gt;* find/print.c (insert_fprintf): Rename some variables for greater
clarity:
format is now segstart, since it points to the start of the part
of the format string we're next going to pass to make_segment.
scan2 is now fmt_inpos (which is a const char*) and is the
scanning position beyond segstart which we're reading to locate
the end of this segment.
scan is now fmt_editpos and is the scanning position at which we
are modifying the format string (for example to change \n in the
format to the value of the '\n' character).
---
 ChangeLog    |   14 +++++++
 find/print.c |  122 ++++++++++++++++++++++++++++++---------------------------
 2 files changed, 78 insertions(+), 58 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index c003e0f..fc6f945 100644
--- a/ChangeLog
+++ b/ChangeLog
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -1,3 +1,17 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
+2011-06-25  James Youngman  &amp;lt;jay&amp;lt; at &amp;gt;gnu.org&amp;gt;
+
+Clarify variable naming in insert_fprintf.
+* find/print.c (insert_fprintf): Rename some variables for greater
+clarity:
+format is now segstart, since it points to the&lt;/pre&gt;</description>
    <dc:creator>James Youngman</dc:creator>
    <dc:date>2011-06-29T09:16:50</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnu.findutils.patches/382">
    <title>Change request proposal for a new Findfunctionality</title>
    <link>http://comments.gmane.org/gmane.comp.gnu.findutils.patches/382</link>
    <description>&lt;pre&gt;Good morning,

This mail just to mention a simple lacking functionality in the Find command :

There is no way to disable the warning messages sent on the error
output, and especially the "Permission non granted" error message sent
for each unaccessible directory met during the research process.

The alone way proposed on various docs or sites is to redirect the
error output on /dev/null. OK, thank's, but that's far to be great.
This is even an invitation to very bad programming, especially by
avoiding the ability to choose through the find parameters the
warnings which are suppressed and those which are not.

So, I submit to the Find maintainers the idea of a change request for
this functionality, maybe through a new option.

Sincerely yours,

Michel Lanne.
&lt;/pre&gt;</description>
    <dc:creator>Michel Lanne</dc:creator>
    <dc:date>2010-11-06T18:08:47</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnu.findutils.patches/372">
    <title>new predicate</title>
    <link>http://comments.gmane.org/gmane.comp.gnu.findutils.patches/372</link>
    <description>&lt;pre&gt;I wanted to submit a patch that is quite short and 
more thought as a feature request. It adds the predicate
"-dtype &amp;lt;regex&amp;gt;" (dtype meaning datatype). The dtype
predicate uses libmagic from the "file" command to get
the *content datatype* of the file in view, then doing a regex on
it. i.e. "echo abc&amp;gt;f.txt; file f.txt" yealds "ASSCII text".
Therefore "file f.txt -dtype .*text.*" would do a regex ".*text.*"
on "ASCII text" (and match). 

The problem this patch addresses is like this:
I have several source project directory with serveral million
files in them. I want to make a backup, however i want 
to only backup text files, (Makefiles, shell sripts, c and
h files etc). Currently I do something like this:
(for f in `find &amp;lt;srcdir&amp;gt; -type f`; do if (file $f | cut -d: -f2 | grep text &amp;amp;&amp;gt; /dev/null ); then echo $f; fi; done) &amp;gt; file.list
Then I use file.list to create a tar.
But, this pipe is very slow (I run it over night so it works but...).
With the above patch I can do:
find &amp;lt;stcdir&amp;gt; -dtype .*text.* &amp;gt;file.list &lt;/pre&gt;</description>
    <dc:creator>Konrad Eisele</dc:creator>
    <dc:date>2010-05-27T20:04:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnu.findutils.patches/348">
    <title>Fix bug #27213: avoid failed assertions fornon-executable directories</title>
    <link>http://comments.gmane.org/gmane.comp.gnu.findutils.patches/348</link>
    <description>&lt;pre&gt;This sequence of patches fixes bug #27213 without issuing a duplicate
error message.  Clearly a NEWS file entry will also be required.


 ChangeLog            |   64 ++++++++++++++++++++++++++++++++++++++
 build-aux/.cvsignore |    1 +
 build-aux/.gitignore |    1 +
 find/defs.h          |   12 ++++++-
 find/find.c          |    8 +++--
 find/ftsfind.c       |   53 +++++++++++++++-----------------
 find/parser.c        |   10 +++---
 find/pred.c          |    8 ++--
 find/sharefile.c     |    2 +-
 find/tree.c          |    1 +
 find/util.c          |   83 +++++++++++++++++++++++++++++++++++++++-----------
 11 files changed, 182 insertions(+), 61 deletions(-)
&lt;/pre&gt;</description>
    <dc:creator>James Youngman</dc:creator>
    <dc:date>2010-04-04T16:28:05</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnu.findutils.patches/320">
    <title>[PATCH] Bug #27213: avoid failed assertions fornon-executable directories.</title>
    <link>http://comments.gmane.org/gmane.comp.gnu.findutils.patches/320</link>
    <description>&lt;pre&gt;Addresses Savannah bug #27213 - https://savannah.gnu.org/bugs/?27213

This used to fail in recent releases:
1. mkdir -p foo/bar
2. chmod a-x foo
3. find foo
4. find foo -ls

Now it will print error messages for the denied permission on foo, but will
not abort completely, and in 3. will even print the name foo/bar, while it
won't do so in 4., as the -ls predicate requires stat information. For now,
4. will print two identical error message. This should get fixed some day.
---
 find/ftsfind.c |   36 ++++++++++++++----------------------
 find/util.c    |   11 +++++++----
 2 files changed, 21 insertions(+), 26 deletions(-)

diff --git a/find/ftsfind.c b/find/ftsfind.c
index 61f1079..a8efdda 100644
--- a/find/ftsfind.c
+++ b/find/ftsfind.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -446,27 +446,19 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; consider_visiting(FTS *p, FTSENT *ent)
     }
   else if (ent-&amp;gt;fts_info == FTS_NS)
     {
-      if (ent-&amp;gt;fts_level == 0)
-{
-  /* e.g., nonexistent starting point */
-  error(0, ent-&amp;gt;fts_errno, "%s",
-safely_quote_err_filename(0, ent-&amp;gt;fts_path));
- &lt;/pre&gt;</description>
    <dc:creator>Martin von Gagern</dc:creator>
    <dc:date>2009-11-22T18:38:58</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnu.findutils.patches/319">
    <title>lib/check-regexprops.sh portability fixes forFreeBSD</title>
    <link>http://comments.gmane.org/gmane.comp.gnu.findutils.patches/319</link>
    <description>&lt;pre&gt;I just applied and pushed the attached patch.

* lib/check-regexprops.sh: Portability fixes for FreeBSD (mktemp
requires an argument, dialect differences in sed regexes).
_______________________________________________
Findutils-patches mailing list
Findutils-patches&amp;lt; at &amp;gt;gnu.org
http://lists.gnu.org/mailman/listinfo/findutils-patches
&lt;/pre&gt;</description>
    <dc:creator>James Youngman</dc:creator>
    <dc:date>2009-08-16T15:18:38</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.gnu.findutils.patches">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.gnu.findutils.patches</link>
  </textinput>
</rdf:RDF>
