From: Steven Dake <sdake@mvista.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Broken compile scripts in LVM
Date: Wed Oct 9 13:40:32 2002 [thread overview]
Message-ID: <3DA46D8B.5010808@mvista.com> (raw)
In-Reply-To: 20021009125221.A23965@sistina.com
[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]
Heinz,
Thanks Jeremy had asked me to forward the patch on. I guess he also did
it himself
-steve
Heinz J . Mauelshagen wrote:
>Steven,
>
>I have changed that in CVS (Branch: LVM_BRANCH_1-0) a couple of days ago
>and announced that on lvm-devel (the list for patches and development
>discussions). Jeremy A. Puhlman pointed it out on October 4th already.
>
>
>On Mon, Oct 07, 2002 at 10:45:19AM -0700, Steven Dake wrote:
>
>
>>Folks,
>>
>>Some of the scripts use echo "string" > /dev/stderr when instead they
>>should be using echo "string" >&2. I have attached a patch that fixes
>>this problem. The result is that in automated builds, the stdout gets
>>stomped if you use the first technique (resulting in loss of logging data).
>>
>>Thanks.
>>
>>-steve
>>
>>
>
>
>
>>diff -u3 lvm-1.0.5/scripts/iopver lvm-1.0.5-fixed/scripts/iopver
>>--- lvm-1.0.5/scripts/iopver Tue Jan 22 06:54:13 2002
>>+++ lvm-1.0.5-fixed/scripts/iopver Thu Oct 3 19:46:40 2002
>>@@ -48,21 +48,19 @@
>> sed -e 's/.*LVM_LIB_IOP_VERSION[[:space:]]*\([[:digit:]]*\).*/\1/'`;
>>
>> if [ -z "$ver1" ]; then
>>- echo "Error: iopver can't determine the IOP version from $file1" > \
>>
>>
><SNIP>
>
>
>>- echo "$new not found" > /dev/stderr
>>+ echo "$new not found" >&2
>> exit 2;
>> fi
>>
>>
>>
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 1789 bytes --]
prev parent reply other threads:[~2002-10-09 13:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 13:31 [linux-lvm] Broken compile scripts in LVM Steven Dake
2002-10-09 5:54 ` Heinz J . Mauelshagen
2002-10-09 13:40 ` Steven Dake [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=3DA46D8B.5010808@mvista.com \
--to=sdake@mvista.com \
--cc=linux-lvm@sistina.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