From: Stan Hoeppner <stan@hardwarefreak.com>
To: "J. Ellis" <jellis@dhnet.us>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: xfsdump INTERRUPT issue
Date: Tue, 04 Dec 2012 16:56:50 -0600 [thread overview]
Message-ID: <50BE7FB2.50902@hardwarefreak.com> (raw)
In-Reply-To: <CCE3BD5D.B0540%jellis@dhnet.us>
On 12/4/2012 1:46 PM, J. Ellis wrote:
> Hi, Dave & Stan, et al--
>
> Are you guys getting this post? I don't see it showing up on the list and
> have had no responses. I'm wondering if the size of the text of the
> requested xfs info I had added is causing an issue getting it posted.
You need to acclimate yourself to the environment/culture of FLOSS
mailing lists. First, don't be giddy. Responses to users will rarely
be immediate. People, both devs and fellow users, contribute help on an
"as time permits" basis. You are not paying for support here. I've
seen some msgs go unanswered for a week or more, both initial requests
and follow ups. I short, don't expect rapid responses and individual
hand holding.
> If not, here's a repost, using a link to the file instead.
>
> http://dhnet.us/xfs/xfs_data_file.odt
Regarding what you think may be lost mail, using an office document
format is not wise, though I don't know if it's allowed here or not. In
general, with FLOSS lists, use plain text, always, whether inline or
attachment. Try not to reference external links as this list is
archived by many sites. Get it all in the archives.
Finally, if you sent me a direct email and my server rejected it you
would receive an NDR pretty quickly. And I don't see any msgs from you
in my spam tagged folder.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-12-04 22:54 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-01 16:03 xfsdump INTERRUPT issue J. Ellis
2012-12-01 17:39 ` Jeffrey Ellis
2012-12-02 1:40 ` Stan Hoeppner
2012-12-03 16:49 ` J. Ellis
2012-12-03 21:34 ` Dave Chinner
2012-12-03 22:27 ` Jeffrey Ellis
2012-12-05 0:32 ` Stan Hoeppner
2012-12-05 1:18 ` J. Ellis
2012-12-05 3:32 ` Stan Hoeppner
2012-12-04 19:46 ` J. Ellis
2012-12-04 22:56 ` Stan Hoeppner [this message]
2012-12-04 23:07 ` Jeffrey Ellis
2012-12-05 22:19 ` Dave Chinner
2012-12-02 21:10 ` Dave Chinner
2012-12-02 21:16 ` Jeffrey Ellis
[not found] <CCE505AA.B05B7%jellis@dhnet.us>
2012-12-06 1:38 ` Stan Hoeppner
2012-12-06 2:08 ` Jeffrey Ellis
2012-12-06 2:40 ` Stan Hoeppner
[not found] ` <6F909666-9DFE-43F1-973D-170B892F9C5B@gmail.com>
2012-12-06 9:29 ` Stan Hoeppner
2012-12-06 10:35 ` Jeffrey Ellis
2012-12-07 10:16 ` Dave Chinner
2012-12-07 16:15 ` Jeffrey Ellis
2012-12-07 22:59 ` Dave Chinner
2012-12-07 23:16 ` Jeffrey Ellis
2012-12-07 21:04 ` Stan Hoeppner
2012-12-07 22:58 ` Dave Chinner
2012-12-07 23:26 ` Stan Hoeppner
2012-12-08 1:31 ` Dave Chinner
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=50BE7FB2.50902@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=jellis@dhnet.us \
--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