From: Pete Zaitcev <zaitcev@redhat.com>
To: guthrie@martnet.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] small patch to ide-tape.c
Date: Tue, 3 Jul 2001 20:36:47 -0400 [thread overview]
Message-ID: <200107040036.f640alb18705@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.994203003.28209.linux-kernel2news@redhat.com>
In-Reply-To: <mailman.994203003.28209.linux-kernel2news@redhat.com>
> This patch adds a missing semicolon that is noticed only if you define
> IDETAPE_DEBUG_LOG_VERBOSE:
>
> John Guthrie
> guthrie@martnet.com
It makes me curious, why do you need to define
IDETAPE_DEBUG_LOG_VERBOSE?
I fixed some stuff with files not restoring properly
with last block corrupt. Talking with Andre and Gadi now.
What is your problem?
-- Pete
next parent reply other threads:[~2001-07-04 0:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.994203003.28209.linux-kernel2news@redhat.com>
2001-07-04 0:36 ` Pete Zaitcev [this message]
2001-07-04 23:02 [PATCH] small patch to ide-tape.c John Guthrie
-- strict thread matches above, loose matches on Subject: below --
2001-07-03 23:27 John Guthrie
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=200107040036.f640alb18705@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=guthrie@martnet.com \
--cc=linux-kernel@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