From: Yngve Svendsen <yngve.svendsen@sun.com>
To: Mel Hatzis <hatzis@juniper.net>,
Dirk Schenkewitz <Dirk.Schenkewitz@interface-ag.com>
Cc: help-gnats <help-gnats@gnu.org>
Subject: Re: too many 'changed' entries
Date: Tue, 29 Apr 2003 21:05:00 -0000 [thread overview]
Message-ID: <5.2.1.1.0.20030429225636.00d3b8d0@ms-etro01-01.norway.sun.com> (raw)
In-Reply-To: <3E833FD7.9050902@juniper.net>
At 10:15 27.03.2003 -0800, Mel Hatzis wrote:
>I noticed this too. In my case, I setup a field as 'required' and
>it wasn't working via gnatsweb, because gnatsweb was inserting a
>newline (thereby making the field look like it had a value).
>
>I fixed it by changing the 'fix_multiline_val' sub, as follows:
(snip)
>This basically prevents whitespace only values from being entered
>as the (multiline) field value which I consider to be a good fix.
>
>This should help you in the case where a newly created PR is edited
>for the first time - since this is when gnatsweb will add the
>newline, thereby changing the field and adding a change log to the
>audit trail.
Nice catch. I have committed the fix. Of course, Gnatsweb's somewhat
reckless sprinkling of newlines should itself be cleaned up, but I dare not
do it for 4.0 after seeing what removing one apparently extraneous newline
did to attachment handling.
- Yngve
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats
next prev parent reply other threads:[~2003-04-29 21:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-24 10:49 Dirk Schenkewitz
2003-03-27 14:06 ` Dirk Schenkewitz
2003-03-27 18:19 ` Mel Hatzis
2003-03-28 16:57 ` Dirk Schenkewitz
2003-04-29 21:05 ` Yngve Svendsen [this message]
2003-05-07 17:05 ` Dirk Schenkewitz
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=5.2.1.1.0.20030429225636.00d3b8d0@ms-etro01-01.norway.sun.com \
--to=yngve.svendsen@sun.com \
--cc=Dirk.Schenkewitz@interface-ag.com \
--cc=hatzis@juniper.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).