public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Larsson <alexl@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Theodore Tso <tytso@mit.edu>, Nicol? Chieffo <84yelo3@gmail.com>,
	Jeremy Allison <jra@samba.org>,
	Szabolcs Szakacsits <szaka@ntfs-3g.org>,
	Josef Bacik <jbacik@redhat.com>,
	linux-fsdevel@vger.kernel.org
Subject: Re: interface to ask is a file is hidden
Date: Mon, 13 Oct 2008 13:39:21 +0200	[thread overview]
Message-ID: <1223897961.20751.40.camel@fatty> (raw)
In-Reply-To: <20081013104336.GA23605@infradead.org>

On Mon, 2008-10-13 at 06:43 -0400, Christoph Hellwig wrote:
> On Mon, Oct 13, 2008 at 12:37:54PM +0200, Alexander Larsson wrote:
> > The traditional unix file systems don't contain "is-hidden" metadata,
> > but some commonly used ones do. What possible bad can come out of
> > letting applications access that information efficiently if they want.
> 
> The bad thing that happens is that it will bloat the kernel with useless
> crap.  And a use case of "make graphical directly listings on foreign
> filesystems look a little less cluttered" is not enough to add a lot of
> code and new interfaces we'll have to maintain forever.

Its only useless and bloat if you think the feature is useless, so we're
once again back to your preferences in applications. I'd like to think
that the opinions of others would be taken into consideration for this
too, and I and others would like this feature.

Unfortunately I don't have time myself atm to implement this, but I hope
someone else is interested in working on this.


  reply	other threads:[~2008-10-13 11:39 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-10 19:22 interface to ask is a file is hidden Nicolò Chieffo
2008-10-10 19:21 ` Josef Bacik
2008-10-10 19:35   ` Jeremy Allison
2008-10-10 20:00     ` Nicolò Chieffo
2008-10-10 19:57       ` Josef Bacik
2008-10-10 20:11         ` Nicolò Chieffo
2008-10-10 21:57       ` Theodore Tso
2008-10-10 22:01         ` Christoph Hellwig
2008-10-13  8:22           ` Alexander Larsson
2008-10-13  9:21             ` Nicolò Chieffo
2008-10-13  9:57             ` Christoph Hellwig
2008-10-13 10:37               ` Nicolò Chieffo
2008-10-13 10:37               ` Alexander Larsson
2008-10-13 10:43                 ` Christoph Hellwig
2008-10-13 11:39                   ` Alexander Larsson [this message]
2008-10-13 20:44                     ` Jörn Engel
2008-10-13 20:50                       ` Christoph Hellwig
2008-10-14  7:20                       ` Alexander Larsson
2008-10-10 22:18         ` Szabolcs Szakacsits
2008-10-10 22:21         ` Nicolò Chieffo
2008-10-10 22:25           ` Christoph Hellwig
2008-10-10 22:33             ` Nicolò Chieffo
2008-10-10 22:36               ` Christoph Hellwig
2008-10-10 22:58                 ` Nicolò Chieffo
2008-10-10 23:12                   ` Szabolcs Szakacsits
2008-10-11  0:10                 ` Bryan Henderson
2008-10-11  1:36               ` Theodore Tso
2008-10-10 22:57         ` Brad Boyer
2008-10-13  7:29         ` Anton Altaparmakov
2008-10-13 10:47           ` Christoph Hellwig
2008-10-13 10:59           ` Alexander Larsson

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=1223897961.20751.40.camel@fatty \
    --to=alexl@redhat.com \
    --cc=84yelo3@gmail.com \
    --cc=hch@infradead.org \
    --cc=jbacik@redhat.com \
    --cc=jra@samba.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=szaka@ntfs-3g.org \
    --cc=tytso@mit.edu \
    /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