public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: kseitz@sources.redhat.com
To: insight-prs@sources.redhat.com, kseitz@sources.redhat.com,
	nobody@sources.redhat.com, sonison_james@hotmail.com
Subject: Re: insight/233: Building insight on HP-UX 11i
Date: Thu, 26 Jun 2003 17:46:00 -0000	[thread overview]
Message-ID: <20030626174644.28970.qmail@sources.redhat.com> (raw)

Synopsis: Building insight on HP-UX 11i

Responsible-Changed-From-To: unassigned->kseitz
Responsible-Changed-By: kseitz
Responsible-Changed-When: Thu Jun 26 17:46:44 2003
Responsible-Changed-Why:
    mine
State-Changed-From-To: open->closed
State-Changed-By: kseitz
State-Changed-When: Thu Jun 26 17:46:44 2003
State-Changed-Why:
    Thank you for the patch. Unfortunately, the file you have patched is part of the libiberty module used by gdb (and consequently insight). From src/MAINTAINERS:
    
    libiberty/; libiberty's part of include/
    gcc: http://gcc.gnu.org
    Changes need to be done in tandem with the official GCC
    sources or submitted to the master file maintainer and brought in via a merge.  Note: approved patches in gcc's libiberty are automatically approved in this libiberty also; feel free to merge them yourself if needed sooner than the next merge. Otherwise, changes are automatically merged, usually within a day.
    
    Please submit to gcc list where the proper maintainer can assess and commit your patch.
    
    (BTW, is this on 5.2.1 or CVS HEAD? We do not maintain old release branches -- only CVS HEAD. If this bug still exists in CVS HEAD, submit to gcc at gnu dot org.)

http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=insight&pr=233


             reply	other threads:[~2003-06-26 17:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-26 17:46 kseitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-06-26 16:33 sonison_james

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=20030626174644.28970.qmail@sources.redhat.com \
    --to=kseitz@sources.redhat.com \
    --cc=insight-gnats@sources.redhat.com \
    --cc=insight-prs@sources.redhat.com \
    --cc=nobody@sources.redhat.com \
    --cc=sonison_james@hotmail.com \
    /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).