public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: no quota output if no usage?
Date: Wed, 26 Nov 2014 18:28:32 -0600	[thread overview]
Message-ID: <54767030.7070706@sandeen.net> (raw)
In-Reply-To: <20141126221845.GE9561@dastard>

On 11/26/14 4:18 PM, Dave Chinner wrote:

>> Or am I missing something ...
> 
> Nope, I'm confusing different reporting command behaviour....

Ok, so back to the original question: think it's cool to drop
the verbose requirement to find out limits when there is 0 usage?

-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2014-11-27  0:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-26 19:26 no quota output if no usage? Eric Sandeen
2014-11-26 21:21 ` Dave Chinner
2014-11-26 21:26   ` Eric Sandeen
2014-11-26 22:18     ` Dave Chinner
2014-11-27  0:28       ` Eric Sandeen [this message]
2014-11-27  9:32         ` Jan Kara
2014-11-28 16:40           ` Eric Sandeen

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=54767030.7070706@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=david@fromorbit.com \
    --cc=xfs@oss.sgi.com \
    /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