Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Pedro Alves <alves.ped@gmail.com>,
	Stan Shebs <stanshebs@earthlink.net>,
	gdb-patches@sourceware.org
Subject: Re: commands.h and cli/cli-decode.h dups
Date: Tue, 03 Jan 2012 17:11:00 -0000	[thread overview]
Message-ID: <20120103171121.GP2730@adacore.com> (raw)
In-Reply-To: <m3aa64hm28.fsf@fleche.redhat.com>

> I am totally in favor of it.
> I think duplication of this sort is a "worst practice".

+1

-- 
Joel


  reply	other threads:[~2012-01-03 17:11 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-22  4:44 FYI: minsyms documentation Tom Tromey
2011-12-22  5:17 ` Joel Brobecker
2011-12-22 20:13 ` Stan Shebs
2011-12-22 20:21   ` Tom Tromey
2011-12-22 21:06     ` Eli Zaretskii
2011-12-23  4:21       ` Stan Shebs
2011-12-23 16:01         ` Eli Zaretskii
2012-01-02 22:08           ` Tom Tromey
2012-01-03  8:17             ` Eli Zaretskii
2011-12-24  7:45         ` Yao Qi
2011-12-24 13:21           ` Eli Zaretskii
2012-01-02 22:08           ` Tom Tromey
2012-01-03  8:18             ` Eli Zaretskii
2011-12-22 21:18     ` Stan Shebs
2011-12-23 10:38   ` Joel Brobecker
2012-01-02 22:14     ` Tom Tromey
2012-01-03  2:53       ` Joel Brobecker
2012-01-03 11:05         ` Pedro Alves
2012-01-03 13:21           ` commands.h and cli/cli-decode.h dups (was: Re: FYI: minsyms documentation) Pedro Alves
2012-01-03 14:57             ` commands.h and cli/cli-decode.h dups Tom Tromey
2012-01-03 17:11               ` Joel Brobecker [this message]
2012-01-05 11:40                 ` Pedro Alves
2012-01-03 11:18 ` FYI: minsyms documentation Pedro Alves
2012-01-15 18:49 ` Michael Eager

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=20120103171121.GP2730@adacore.com \
    --to=brobecker@adacore.com \
    --cc=alves.ped@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=stanshebs@earthlink.net \
    --cc=tromey@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