public inbox for gnats-prs@sourceware.org help / color / mirror / Atom feed
From: m_venkateshkumar@mindtree.com To: gnats-gnats@sourceware.cygnus.com Subject: gnats/186: gnats-queue not getting empty even after PR has been sent Date: Wed, 02 May 2001 00:04:00 -0000 [thread overview] Message-ID: <20010502065811.12968.qmail@sourceware.cygnus.com> (raw) >Number: 186 >Category: gnats >Synopsis: gnats-queue not getting empty even after PR has been sent >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Wed May 02 00:04:00 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Net >Release: unknown-1.0 >Organization: >Environment: Linux neat 2.2.14-5.0 #1 Tue Mar 7 21:07:39 EST 2000 i686 unknown >Description: I create a PR using the send-pr program. I can see that this PR gets queued in the gnats-queue directory. When I run queue-pr --run, the sender and the person responsible get the mail. But, the PR DOES NOT get removed from the gnats-queue directory, and stays there, but this time, with another uniquely generated file name. Because of this, the same PR is being sent to the person responsible for many many times. In my machine, I was not present for 5 days, and the entire disk became full because of this problem!! Can somebody tell me why this is happening? >How-To-Repeat: Dont know. This condition was not happening for about 3 days after I installed GNATS. This problem suddenly started appearing since 5 days. Now, whenever I do a send-pr, this problem is occuring. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-05-02 0:04 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-05-02 0:04 m_venkateshkumar [this message] 2001-05-02 5:04 Yngve Svendsen
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=20010502065811.12968.qmail@sourceware.cygnus.com \ --to=m_venkateshkumar@mindtree.com \ --cc=gnats-gnats@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: linkBe 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).