public inbox for firstname.lastname@example.org
help / color / mirror / Atom feed
* gnats/26: index gets messed up if responsible is empty in categories
@ 1999-11-13 3:44 sohail
0 siblings, 0 replies; only message in thread
From: sohail @ 1999-11-13 3:44 UTC (permalink / raw)
>Synopsis: index gets messed up if responsible is empty in categories
>Arrival-Date: Sat Nov 13 03:44:00 PST 1999
>Originator: Sohail Aslam
Redhat linux 6.0, gnats 3.113, gnatsweb 2.5
If the reponsible field is left empty, e.g.,
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.
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.
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.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~1999-11-13 3:44 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-11-13 3:44 gnats/26: index gets messed up if responsible is empty in categories sohail
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).