From: Ruediger Meier <sweet_f_a@gmx.de>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: some quesion about test_uuidd
Date: Mon, 8 Feb 2016 13:55:22 +0100 [thread overview]
Message-ID: <201602081355.23476.sweet_f_a@gmx.de> (raw)
In-Reply-To: <20160208120848.xno2uesyuyc4y4wh@ws.net.home>
On Monday 08 February 2016, Karel Zak wrote:
> On Mon, Feb 08, 2016 at 11:46:04AM +0100, Ruediger Meier wrote:
> > Hi,
> >
> > since 963f128c we are building test_uuidd in tests/helpers.
> >
> > Where do we use test_uuidd at the moment?
>
> I don't think we use it, it's mostly for manual testing now.
>
> > Because it breakes "configure --disable-libuuid we should guard the
> > test_uuidd build either bei BUILD_LIBUUID or by BUILD_UUIDD. Maybe
> > it should also be moved to misc-utils/ (where uuidd lives) or
> > libuuid/src/ (where test_uuid lives). Opinions?
>
> Yes, misc-utils/test_uuidd.c would be better place for the code.
I will do that.
cu,
Rudi
prev parent reply other threads:[~2016-02-08 12:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 10:46 some quesion about test_uuidd Ruediger Meier
2016-02-08 12:08 ` Karel Zak
2016-02-08 12:55 ` Ruediger Meier [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=201602081355.23476.sweet_f_a@gmx.de \
--to=sweet_f_a@gmx.de \
--cc=kzak@redhat.com \
--cc=util-linux@vger.kernel.org \
/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