From: Avi Kivity <avi@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: inconsistent use of $TMP vs. $TMPDIR
Date: Sun, 26 Sep 2010 15:10:20 +0200 [thread overview]
Message-ID: <4C9F463C.9010102@redhat.com> (raw)
In-Reply-To: <4C9D12E0.9050001@redhat.com>
On 09/24/2010 11:06 PM, Eric Blake wrote:
> I noticed today that various kvm source files are inconsistent on the
> use of $TMP vs. $TMPDIR:
>
> $ git grep -l '\$TMP\b' | cat
> scripts/Kbuild.include
> tools/perf/feature-tests.mak
> $ git grep -l '\$TMPDIR\b' | cat
> Documentation/lguest/extract
>
> According to POSIX, you should probably be using $TMPDIR instead of
> $TMP when referring to the preferred temporary directory location.
>
> http://www.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.html#tag_08_03
>
>
These are not kvm specific issues. Please use MAINTAINERS to report to
the maintainer of the affected subsystems (lguest, kbuild).
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-09-26 13:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-24 21:06 inconsistent use of $TMP vs. $TMPDIR Eric Blake
2010-09-26 13:10 ` Avi Kivity [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=4C9F463C.9010102@redhat.com \
--to=avi@redhat.com \
--cc=eblake@redhat.com \
--cc=kvm@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