From: "Stuart Stevens" <stuart_stevens@sierralogic.com>
To: "'Stuart Stevens'" <stuart_stevens@sierralogic.com>,
<help-gnats@gnu.org>
Subject: RE: Unparseable replies from GNATS server
Date: Thu, 26 Aug 2004 20:15:00 -0000 [thread overview]
Message-ID: <E1Bznwz-0007ej-DG@lists.gnu.org> (raw)
In-Reply-To:
Ok, I have a working solution to get around two different problems. The
Note has to be before Notes and Notes needs a default value. I need to do
some more analysis to propose a code change.
Here is my currently working solution for an append field.
field "Note" {
multitext
on-change {
append-to-field "Notes" {
"\n================================================\n%D %s\n\n%s\n"
"$CurrentDate" "$EditUserEmailAddr" "$NewValue"
}
}
on-change {
set-field "Note" {
""
}
}
on-change {
add-audit-trail
}
}
field "Notes" {
multitext {
default ""
}
read-only
}
-----Original Message-----
From: Stuart Stevens [mailto:stuart_stevens@sierralogic.com]
Sent: Thursday, August 12, 2004 10:27 AM
To: 'Stuart Stevens'; help-gnats@gnu.org
Subject: RE: Unparseable replies from GNATS server
Hi
Does anybody have a recommendation on how to add an append-only comments
field?
I would like edits to allow new additions to the field and views to show the
whole field.
Stuart
-----Original Message-----
From: Stuart Stevens [mailto:stuart_stevens@sierralogic.com]
Sent: Wednesday, August 04, 2004 7:49 PM
To: 'Stuart Stevens'; help-gnats@gnu.org
Subject: RE: Unparseable replies from GNATS server
In edit.c, set_field is being called with old_value set to 0x00.
if ((old_value == NULL && new_value != NULL)
|| (new_value == NULL && old_value != NULL)
|| (new_value != old_value && strcmp (old_value, new_value) != 0))
{
/* Ignore changes to readonly fields. */
if (fieldDefForIndex (field)->readonly)
{
fieldsChanged[x] = 0;
set_field (new_pr, field, old_value, err);
}
else
{
fieldsChanged[x] = 1;
}
}
-----Original Message-----
From: Stuart Stevens [mailto:stuart_stevens@sierralogic.com]
Sent: Wednesday, August 04, 2004 5:08 AM
To: 'Stuart Stevens'; help-gnats@gnu.org
Subject: RE: Unparseable replies from GNATS server
I am running GNATS 4.0 on Linux - Red Hat 9. I pulled the TOT and rebuilt
this morning. I then run the daemon directly and I got a memory fault. The
daemon fails with the following field "Comment-new" added to dbconfig:
field "Comments" {
multitext
read-only
}
field "Comment-new" {
multitext
on-change {
append-to-field "Comments" {
"Comment added by %s on %D\n\n%s"
"$EditUserEmailAddress" "$CurrentDate" "$NewValue"
}
}
on-change {
set-field "Comment-new" {
""
}
}
}
I issued the following commands:
lock 2511 stuart
editaddr stuart
edit 2511
<email with changes>
Next step is to get into the debugger.
Any ideas?
Thanks
Stuart
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnats
next reply other threads:[~2004-08-25 2:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 20:15 Stuart Stevens [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-13 3:05 Stuart Stevens
2004-08-05 10:23 Stuart Stevens
2004-08-04 12:08 Stuart Stevens
2004-08-04 19:02 ` Stuart Stevens
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=E1Bznwz-0007ej-DG@lists.gnu.org \
--to=stuart_stevens@sierralogic.com \
--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).