From: Alex Elder <aelder@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 01/12] xfsprogs: some things aren't all that special
Date: Mon, 10 Jan 2011 14:22:36 -0600 [thread overview]
Message-ID: <1294690956.5374.48.camel@doink> (raw)
In-Reply-To: <20110110201137.GA27277@infradead.org>
On Mon, 2011-01-10 at 15:11 -0500, Christoph Hellwig wrote:
> Also you've stopped overwriting orphanage_ino if it already exists.
Actually, I had noticed I did more (or worse) than
just that. Once orphanage_ino has been saved, my
change no longer says it should avoid obfuscating
it. (Or is that what you mean by "overwriting"?)
Anyway, I noticed that problem the other day and
thought I'd fix it if I had a chance to re-post.
Thanks.
-Alex
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-01-10 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-30 20:39 [PATCH 01/12] xfsprogs: some things aren't all that special Alex Elder
2011-01-10 20:11 ` Christoph Hellwig
2011-01-10 20:22 ` Alex Elder [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=1294690956.5374.48.camel@doink \
--to=aelder@sgi.com \
--cc=hch@infradead.org \
--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