Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Removal of markup annotations
Date: Wed, 28 Sep 2005 03:45:00 -0000	[thread overview]
Message-ID: <20050928034539.GA29542@nevyn.them.org> (raw)
In-Reply-To: <20050928001644.A76A383B3@kahikatea.snap.net.nz>

On Wed, Sep 28, 2005 at 12:16:44PM +1200, Nick Roberts wrote:
> Nick Roberts (Wed, 15 Jun 2005 15:16:03 +1200) writes:
>  > 
>  > Here's the patch for the removal of some of the level 2 annotations that I
>  > referred to yesterday.  It primarily removes the markup annotations that
>  > worked just with level (annotation_level == 2) and leaves those which also
>  > worked with level 3 (annotation_level > 2)...  
> 
> Since no-one seems that interested, I would like to submit this much smaller
> patch that just removes the breakpoints-invalid and frames-invalid from level
> 3, which AFAIK only Emacs uses.
> 
> Nick
> 
> 
> 2005-09-28  Nick Roberts  <nickrob@snap.net.nz>
> 
> 	* annotate.c (breakpoints_changed, annotate_frames_invalid)
> 	(_initialize_annotate): Print breakpoints-invalid and
> 	frames-invalid for level 2 annotations only.

I'm indifferent on removing them entirely, but I support removing them
from level three.  However other programs have definitely started to
use level 3 - e.g. google found clewn.sf.net/clewn.txt.html.  Actually
that was the only one I could easily turn up.  Want to double-check
that it doesn't use these?

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  parent reply	other threads:[~2005-09-28  3:45 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-15  3:19 Nick Roberts
2005-06-15 15:41 ` Bob Rossi
2005-06-15 23:07   ` Nick Roberts
2005-06-15 23:35     ` Bob Rossi
2005-06-15 23:58       ` Nick Roberts
2005-06-21  1:41         ` Bob Rossi
2005-06-21  6:00           ` Nick Roberts
2005-06-21 10:22             ` Bob Rossi
2005-06-16  3:28       ` Eli Zaretskii
2005-06-15 17:06 ` Eli Zaretskii
2005-06-15 21:41   ` Nick Roberts
2005-06-20 11:54   ` Nick Roberts
2005-06-20 19:29     ` Eli Zaretskii
2005-06-20 21:48       ` Nick Roberts
2005-06-21  3:41         ` Eli Zaretskii
2005-06-21  7:32           ` Nick Roberts
     [not found]             ` <uacljzbgq.fsf@gnu.org>
2005-06-21 23:47               ` Nick Roberts
2005-06-22  3:25                 ` Eli Zaretskii
2005-06-22  6:22                   ` Nick Roberts
2005-07-03 19:04 ` Daniel Jacobowitz
2005-07-03 22:13   ` Nick Roberts
2005-07-03 22:45     ` Daniel Jacobowitz
2005-09-28  0:17 ` Nick Roberts
2005-09-28  2:39   ` Bob Rossi
2005-09-28  3:45   ` Daniel Jacobowitz [this message]
2005-09-28  6:40     ` Nick Roberts
2005-09-28 13:11       ` Daniel Jacobowitz
2005-09-28 22:52         ` Nick Roberts
2005-09-28 22:56           ` Daniel Jacobowitz

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=20050928034539.GA29542@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    /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