Processed: gcc: submitted Debian report #204391 to gcc-gnats as PR 11927

To: doko@debian.org
Cc: debian-bugs-forwarded@lists.debian.org (#204391), Debian GCC maintainers <debian-gcc@lists.debian.org>(libstdc++5 #204391)
Subject: Processed: gcc: submitted Debian report #204391 to gcc-gnats as PR 11927
From: owner@bugs.debian.org (Debian Bug Tracking System)
Date: Fri, 15 Aug 2003 08:48:11 -0500
Message-id: <[🔎] handler.s.C.10609548792545.transcript@bugs.debian.org>
In-reply-to: <E19nepP-0003sU-6t@tango.net.local>
References: <E19nepP-0003sU-6t@tango.net.local>

Processing commands for control@bugs.debian.org:

> # submitted Debian report #204391 to gcc-gnats as PR 11927
> # http://gcc.gnu.org/PR11927
> forwarded 204391 http://gcc.gnu.org/PR11927
Bug#204391: octave: Segfault on bad function name
Noted your statement that Bug has been forwarded to http://gcc.gnu.org/PR11927.

> retitle 204391 [PR 11927] [powerpc] wrong code, buffer overflow?
Bug#204391: octave: Segfault on bad function name
Changed Bug title.

> tags 204391 + upstream
Bug#204391: [PR 11927] [powerpc] wrong code, buffer overflow?
Tags were: moreinfo
Tags added: upstream

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

Reply to:

Prev by Date: Processed: Re: Bug#204391: octave: Segfault on bad function name
Next by Date: [Bug target/11927] [powerpc] wrong code, buffer overflow?
Previous by thread: Processed: Re: Bug#204391: octave: Segfault on bad function name
Next by thread: [Bug target/11927] [powerpc] wrong code, buffer overflow?
Index(es):
- Date
- Thread