Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] MI: Add value field to output of -var-create
Date: Thu, 08 Feb 2007 20:07:00 -0000	[thread overview]
Message-ID: <17867.33519.93541.517510@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20070208175749.GA17845@nevyn.them.org>

> Thanks.  This is OK.

Comitted.

 > > 2007-02-05  Nick Roberts  <nickrob@snap.net.nz>
 > > 
 > > 	* gdb.mi/mi-var-block.exp, gdb.mi/mi2-var-block.exp,
 > > 	* gdb.mi/mi-var-child.exp, gdb.mi/mi2-var-child.exp,
 > > 	* gdb.mi/mi-var-child-f.exp, gdb.mi/mi-var-cmd.exp,
 > > 	* gdb.mi/mi2-var-cmd.exp, gdb.mi/mi-var-display.exp,
 > > 	* gdb.mi/mi2-var-display.exp, gdb.mi/gdb701.exp,
 > >         * gdb.mi/gdb792.exp, gdb.mi/gdb792.exp,
 > > 	* lib/mi-support.exp:
 > > 	Update tests to include value field in output of -var-create.
 > 
 > Please only put the * on the first line - a comma shouldn't be
 > followed by a *.

It doesn't display properly in Emacs without a * on each line e.g look at
this change in Emacs:

2007-02-07  Daniel Jacobowitz  <dan@codesourcery.com>

	* gdb.xml/bad-include.xml, gdb.xml/inc-2.xml, gdb.xml/inc-body.xml,
	gdb.xml/includes.xml, gdb.xml/tdesc-xinclude.exp: New files.

The files on the second line are displayed as normal text.

I kept the *'s but removed the commas.  This style is used by the Emacs
project, at least.  The convention used there is that if different files
have different changes then a blank line is left between the ChangeLog entries,
but if the changes are the same then the entries are contiguous.


-- 
Nick                                           http://www.inet.net.nz/~nickrob


  reply	other threads:[~2007-02-08 20:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-02 10:07 Nick Roberts
2007-01-04 20:20 ` Vladimir Prus
2007-01-04 23:22   ` Nick Roberts
2007-01-04 23:24     ` Daniel Jacobowitz
2007-01-05  7:40     ` Vladimir Prus
2007-01-05 15:07 ` Daniel Jacobowitz
2007-01-05 21:30   ` Nick Roberts
2007-01-07 23:32     ` Daniel Jacobowitz
2007-01-18  9:09   ` Nick Roberts
2007-01-20 19:09     ` Daniel Jacobowitz
2007-01-20 21:53       ` Nick Roberts
2007-02-03  4:54         ` Nick Roberts
2007-02-04 14:10           ` Daniel Jacobowitz
2007-02-04 21:42             ` Nick Roberts
2007-02-08 17:58               ` Daniel Jacobowitz
2007-02-08 20:07                 ` Nick Roberts [this message]
2007-02-08 20:25                   ` Daniel Jacobowitz
2007-02-08 20:27                     ` Daniel Jacobowitz
2007-02-08 20:37                       ` Nick Roberts
2007-02-08 20:37                         ` Daniel Jacobowitz
2007-02-08 20:44                     ` Nick Roberts

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=17867.33519.93541.517510@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=drow@false.org \
    --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