From: Christoph Hellwig <hch@infradead.org>
To: Christian Kujau <lists@nerdbynature.de>
Cc: Christoph Hellwig <hch@infradead.org>, linux-xfs@oss.sgi.com
Subject: Re: xfstests: nslookup not found
Date: Sun, 19 Jul 2009 20:16:37 -0400 [thread overview]
Message-ID: <20090720001637.GA31674@infradead.org> (raw)
In-Reply-To: <alpine.DEB.2.01.0907191653240.6439@bogon>
On Sun, Jul 19, 2009 at 04:57:19PM -0700, Christian Kujau wrote:
> On Sun, 19 Jul 2009 at 14:20, Christoph Hellwig wrote:
> > Can you resend a patch that just moves _get_fqdn and the check for
> > nslookup from common* into the "new" script?
>
> If I understand correctly, maybe something like this would be acceptable?
>
> I was tempted to use "hostname -f" to give out the fqdn, but appaerently
> not every hostname knows "-f" and I did not want to let the whole script
> fail just because nslookup is not in place.
Yes, that's exactly it. Can you resend it with a proper subject,
description and add your Signed-off-by tag?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-07-20 0:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-19 17:57 xfstests: nslookup not found Christian Kujau
2009-07-19 18:20 ` Christoph Hellwig
2009-07-19 22:26 ` Eric Sandeen
2009-07-19 23:57 ` Christian Kujau
2009-07-20 0:16 ` Christoph Hellwig [this message]
2009-07-20 1:46 ` [PATCH] don't fail if nslookup is not found (was: xfstests: nslookup not found) Christian Kujau
2009-07-20 9:32 ` Christoph Hellwig
2009-07-20 17:03 ` Christian Kujau
2009-07-20 17:56 ` [PATCH] don't fail if nslookup is not found 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=20090720001637.GA31674@infradead.org \
--to=hch@infradead.org \
--cc=linux-xfs@oss.sgi.com \
--cc=lists@nerdbynature.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.