public inbox for gnats-prs@sourceware.org help / color / mirror / Atom feed
From: sohail@techlogix.com To: gnats-gnats@sourceware.cygnus.com Subject: gnats/26: index gets messed up if responsible is empty in categories Date: Sat, 13 Nov 1999 03:44:00 -0000 [thread overview] Message-ID: <19991113113836.15226.qmail@sourceware.cygnus.com> (raw) >Number: 26 >Category: gnats >Synopsis: index gets messed up if responsible is empty in categories >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Sat Nov 13 03:44:00 PST 1999 >Closed-Date: >Last-Modified: >Originator: Sohail Aslam >Release: 3.113 >Organization: >Environment: Redhat linux 6.0, gnats 3.113, gnatsweb 2.5 >Description: If the reponsible field is left empty, e.g., test:*Test Category:: ^empty here The >Responsible: field in the PR is left empty after the :. This causes the index to get a duplicate entry. Here is how the execution in the gnats code proceeds. In file gen-index.c, the routine do_category calls read_pr to pick up the PR from the PR file. gen-index then calls create_index_entry(line). The character string "line" is passed in which the index entry of the currently read PR is to be returned. Before proceeding, create_index_entry (in file index.c) checks whether the PR has responsible field value. If not, create_index_entry returns immediately. The effect is that the string "line" in do_category retains the index line from the last good PR. The index file ends with a duplicate entry. create_index_entry also returns if ARRIVAL_DATE, LAST_MODIFIED and CLOSED_DATE are found to be empty in the PR. >How-To-Repeat: 1. Set responsible to null (::) for a category. Post a PR. Look at the >Reponsible field in the PR once queue-pr has run. Run gen-index; a duplicate entry will appear. >Fix: gen-index and friends should should take a more appropriate action than to simply return when RESPONSIBLE, CLOSED_DATE, ARRIVAL_DATE and LAST_MODIFIED fields are found to be empty in a PR. >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~1999-11-13 3:44 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19991113113836.15226.qmail@sourceware.cygnus.com \ --to=sohail@techlogix.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).