public inbox for gnats-prs@sourceware.org
help / color / mirror / Atom feed
From: Yngve Svendsen <yngve.svendsen@clustra.com>
To: nobody@sourceware.cygnus.com
Cc: gnats-prs@sourceware.cygnus.com
Subject: Re: gnatsweb/192: problem with file-pr, problem with query-pr
Date: Fri, 11 May 2001 06:04:00 -0000	[thread overview]
Message-ID: <20010511130401.30318.qmail@sourceware.cygnus.com> (raw)

The following reply was made to PR gnatsweb/192; it has been noted by GNATS.

From: Yngve Svendsen <yngve.svendsen@clustra.com>
To: kitdun@swc.sec.samsung.co.kr,gnats-gnats@sourceware.cygnus.com
Cc:  
Subject: Re: gnatsweb/192: problem with file-pr, problem with query-pr 
Date: Fri, 11 May 2001 10:56:51 +0200

 At 07:51 11.05.2001 +0000, kitdun@swc.sec.samsung.co.kr wrote:
 >When I use gnatsweb with 
 >parsemime.pl( http://sources.redhat.com/gnats/mimedecode.html ),
 >
 >create pr returns with two error.
 >
 >1) problem with file-pr
 >         failure reading PR
 >
 >2) problem with query-pr
 >         renamed `gnats2shLW5' to `.gnats2shLW5' pending human intervention.
 
 This should porbably be sent directly to the gnats-devel mailing list as 
 parsemime.pl is not part of the official Gnats distribution.
 
 Could you go to the gnats-queue directory, do an "ls -al" in that directory 
 and send the output to me. I need to know how big the files are that come 
 out of the other side of the filter.
 
 Does this only happen when you send in PRs with attachments, or does it 
 always happen?
 
 Yngve Svendsen
 IS Engineer
 Clustra AS, Trondheim, Norway
 yngve.svendsen@clustra.com
 


             reply	other threads:[~2001-05-11  6:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-11  6:04 Yngve Svendsen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-05-11  0:54 kitdun

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=20010511130401.30318.qmail@sourceware.cygnus.com \
    --to=yngve.svendsen@clustra.com \
    --cc=gnats-prs@sourceware.cygnus.com \
    --cc=nobody@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).