This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Daniel Berlin <dberlin@dberlin.org> wrote:
Because a new addition to the audit-trail doesn't mean that the PR was really rechecked. Modified doesn't imply reconfirmed.
Hence the need for a boolean flag. I can have it auto-reset them every 30 days a bug isn't touched or something, if you like, as a cronjob. There's still no need for a full timestamp, because it knows when the flag was changed anyway.
It's not a boolean flag.
Either a bug has been confirmed 2 day ago, 2 weeks ago, 2 months ago or 2 years go, they're all different situations.
Since
GNATS doesn't have a field for this, we're putting it into the synopsis.
I would not mind Bugzilla to have such a timestamp.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |