Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Elena Zannoni <ezannoni@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: PATCH: operate-and-get-next
Date: Tue, 13 Nov 2001 10:55:00 -0000	[thread overview]
Message-ID: <87r8qklwny.fsf@creche.redhat.com> (raw)
In-Reply-To: Elena Zannoni's message of "Mon, 26 Nov 2001 21:42:57 -0500"

>>>>> "Elena" == Elena Zannoni <ezannoni@cygnus.com> writes:

Tom> [ operate-and-get-next ]

Elena> Thanks Tom, yes, please commit it.

Thanks, will do.  I took the opportunity to sneak in a NEWS update,
appended.  If this was wrong or if you want me to change the text,
please tell me and I'll do so.

Tom

Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.37
diff -u -r1.37 NEWS
--- NEWS 2001/11/27 03:09:44 1.37
+++ NEWS 2001/11/27 03:25:53
@@ -12,6 +12,10 @@
 The new `--args' feature can be used to specify command-line arguments
 for the inferior from gdb's command line.
 
+* Changes to key bindings
+
+There is a new `operate-and-get-next' function bound to `C-o'.
+
 *** Changes in GDB 5.1:
 
 * New native configurations


WARNING: multiple messages have this Message-ID

From: Tom Tromey <tromey@redhat.com>
To: Elena Zannoni <ezannoni@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: PATCH: operate-and-get-next
Date: Mon, 26 Nov 2001 19:26:00 -0000	[thread overview]
Message-ID: <87r8qklwny.fsf@creche.redhat.com> (raw)
Message-ID: <20011126192600.-lxXrMOnlBQ7N8Pp0eCEw64igeWRuK3yUzJ-3K_9pNk@z> (raw)
In-Reply-To: <15362.64945.737893.148419@krustylu.cygnus.com>

>>>>> "Elena" == Elena Zannoni <ezannoni@cygnus.com> writes:

Tom> [ operate-and-get-next ]

Elena> Thanks Tom, yes, please commit it.

Thanks, will do.  I took the opportunity to sneak in a NEWS update,
appended.  If this was wrong or if you want me to change the text,
please tell me and I'll do so.

Tom

Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.37
diff -u -r1.37 NEWS
--- NEWS 2001/11/27 03:09:44 1.37
+++ NEWS 2001/11/27 03:25:53
@@ -12,6 +12,10 @@
 The new `--args' feature can be used to specify command-line arguments
 for the inferior from gdb's command line.
 
+* Changes to key bindings
+
+There is a new `operate-and-get-next' function bound to `C-o'.
+
 *** Changes in GDB 5.1:
 
 * New native configurations


  reply	other threads:[~2001-11-27  3:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <15362.64511.39505.586347@krustylu.cygnus.com>
2001-11-13  9:48 ` Elena Zannoni
2001-11-13 10:55   ` Tom Tromey [this message]
2001-11-26 19:26     ` Tom Tromey
2001-11-26 23:43     ` Eli Zaretskii
2001-11-14 11:56       ` Eli Zaretskii
2001-11-26 18:36   ` Elena Zannoni
2001-10-03 16:05 Tom Tromey
2001-10-04  0:00 ` Eli Zaretskii
2001-10-04 18:16   ` Tom Tromey
2001-10-09 12:06     ` Eli Zaretskii
2001-10-09 12:48       ` Tom Tromey
2001-10-10 17:53 ` Elena Zannoni
2001-10-13 10:24   ` Tom Tromey
2001-10-15  9:13     ` Elena Zannoni
     [not found]       ` <878zdibdxb.fsf@creche.redhat.com>
2001-11-08 16:01         ` Elena Zannoni
2001-11-08 18:22           ` Tom Tromey
2001-11-09 13:16             ` Eli Zaretskii

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=87r8qklwny.fsf@creche.redhat.com \
    --to=tromey@redhat.com \
    --cc=ezannoni@cygnus.com \
    --cc=gdb-patches@sources.redhat.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