public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: Chad Walstrom <chewie@wookimus.net>
To: help-gnats@gnu.org
Subject: Re: GNATS Changes
Date: Mon, 20 Sep 2004 16:34:00 -0000	[thread overview]
Message-ID: <20040920162142.GH30447@wookimus.net> (raw)
In-Reply-To: <E1C8QtR-0003iF-0x@lists.gnu.org>


[-- Attachment #1.1: Type: text/plain, Size: 2578 bytes --]

Stuart Stevens wrote:
> I am considering some of the following changes to gnats.  How do I
> find out what is being worked on and whether any of these changes have
> already been incorporated into GNATS?

The ChangeLog in each directory contains changes that have taken place
to the source code or documentation.  The ChangeLog files are maintained
manually with the format found in the GNU Coding Standards[1]_.

Recently, I updated the TODO files using the devtodo tool.  Use of this
tool is not mandatory as you can edit the .todo file manually (it is
pretty straight forward XML) and ask someone to generate the TODO file
for you.

> 1.  Change Audit-Trail field to support a header so that the changed
> by and when fields do not have to repeat for each change.
> 
> 2.  Support for append-only field.  There would be a format for how
> the text is appended.  There would be support for the append to be at
> the top or bottom of the previous text.

Currently listed as 5.8 in the TODO list, reportedly dependant upon
updating access control mechanisms (5.6).  The 5 sublist is currently
the "Unassigned" list, where these enhancements are not yet targeted for
a particular release.

> 3.  Command to list subfield names.  I did not see this anywhere.

Nice idea.

> 4.  Flag to identify fields that have subfields.  Can flags be added
> without breaking any existing interfaces?

I'd have to look more closely.  I'm not as familiar with the code or
protocol as those more experience with the code base.  Perhaps when I
get my two weeks of "vacation", I'll have time to study this better.

> 5.  Notify support for sub field when the sub field is a multi-enum.

I would probably lump 3, 4, and 5 as a sub-list of TODO's for a single
goal: Enhance Subfield Processing.

> 6.  Hooks in the create and edit to validate fields

5.3 is listed as "Add script hooks, probably for edit formats and such.
Need to think about how to integrate in changes to the PR done by the
script"

There was also mention of hooks with some of the enhancements that Mel
was planning on rolling into GNATS in the sometime near future.  Take a
look at the list archives for the discussion.  In June '04 [2]_, there was lots
of discussion about enhancing GNATS.

References
==========
.. [1] http://www.gnu.org/prep/standards_toc.html
.. [2] http://lists.gnu.org/archive/html/help-gnats/2004-06/threads.html

-- 
Chad Walstrom <chewie@wookimus.net>           http://www.wookimus.net/
           assert(expired(knowledge)); /* core dump */

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnats

      reply	other threads:[~2004-09-20 16:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-18  0:01 Stuart Stevens
2004-09-20 16:34 ` Chad Walstrom [this message]

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=20040920162142.GH30447@wookimus.net \
    --to=chewie@wookimus.net \
    --cc=help-gnats@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).