From: Theodore Tso <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH V2] lsattr: return error values
Date: Sun, 21 Jun 2009 21:48:01 -0400 [thread overview]
Message-ID: <20090622014801.GA26079@mit.edu> (raw)
In-Reply-To: <4A3AC4DB.2030609@redhat.com>
On Thu, Jun 18, 2009 at 05:51:07PM -0500, Eric Sandeen wrote:
> (hastily redone before I leave for a few days, hope this
> is sane, review welcome) :)
>
> lsattr doesn't return an error if you point it at a file that
> doesn't exist.
>
> This is slightly trickier because it can take more than one
> file as an arg, but ls seems to report an error if any occurred,
> so this does the same, it'll report the last error that was
> encountered.
>
> Addresses-RedHat-Bugzilla: #489841
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Thanks, applied.
- Ted
prev parent reply other threads:[~2009-06-22 1:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 21:59 [PATCH] lsattr: return error values Eric Sandeen
2009-06-18 22:35 ` Eric Sandeen
2009-06-18 22:51 ` [PATCH V2] " Eric Sandeen
2009-06-22 1:48 ` Theodore Tso [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=20090622014801.GA26079@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.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;
as well as URLs for NNTP newsgroup(s).