Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Luis Machado <lgustavo@codesourcery.com>
Cc: "'gdb-patches@sourceware.org'" <gdb-patches@sourceware.org>,
	 Pedro Alves <palves@redhat.com>, Tom Tromey <tromey@redhat.com>
Subject: Re: [PATCH] Refactor common/target-common into meaningful bits
Date: Sat, 17 Aug 2013 04:01:00 -0000	[thread overview]
Message-ID: <520EF596.9020307@codesourcery.com> (raw)
In-Reply-To: <520E3BE9.9010402@codesourcery.com>

I see some gotchas with this patch (on Makefile.in etc).

I'll get those fixed and will submit an updated version.

On 08/16/2013 11:49 AM, Luis Machado wrote:
> Hi,
>
> This is an updated version of the patch that drops the target-* naming,
> creates a new directory named "target" under src/gdb and renames the
> files target-<something>.* to <something.*.
>
> Based on previous discussions, it seems this is what it should look like
> in the future.
>
> One of the differences now is the inclusion of, for example,
> "target/resume.h" instead of "resume.h". It looks more intuitive this way.
>
> Ok?
>
> Luis
>
> On 08/01/2013 02:09 PM, Luis Machado wrote:
>> Hi,
>>
>> After the previous discussion
>> (http://sourceware.org/ml/gdb-patches/2013-07/msg00840.html), follows a
>> patch to refactor the ill-named target-common.[c|h] files into something
>> a bit more meaningful.
>>
>> First, it seems like a good idea to stablish a  more meaningful
>> directory structure as well, so we are moving target-common.[c|h] from
>> the "common" dir to the new "target" dir. This new directory will hold
>> anything more backend-related. For now it contains only generic target
>> definitions and functions.
>>
>> I've broken target-common.[c|h] into the following:
>>
>> - target-resume.h: Definition for resume_kind.
>>
>> - target-waitstatus.[c|h]: Definitions and code for anything related to
>> waitstatus.
>>
>> - target-wait.h: A tiny bit that does not seem to fit properly in the
>> waitstatus files, so it is left here.
>>
>> As usual, Makefile and other dependencies have been adjusted. Everything
>> builds fine and does not show any regressions.
>>
>> The copyright headers have been adjusted and cleaned up to remove
>> contribution messages.
>>
>> Comments over 70 columns have also been adjusted for this patch.
>>
>> Thoughts?
>>
>> Luis
>


  reply	other threads:[~2013-08-17  4:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-01 17:09 Luis Machado
2013-08-01 17:50 ` Tom Tromey
2013-08-01 17:52   ` Luis Machado
2013-08-02  9:29     ` Pedro Alves
2013-08-02 20:48       ` Tom Tromey
2013-08-05 10:44         ` Pedro Alves
2013-08-05 15:33           ` Luis Machado
2013-08-05 19:12           ` Tom Tromey
2013-08-05 19:21             ` Mark Kettenis
2013-08-06  8:48               ` Pedro Alves
2013-08-04 12:35       ` Yao Qi
2013-08-01 17:54   ` Pedro Alves
2013-08-16 14:49 ` Luis Machado
2013-08-17  4:01   ` Luis Machado [this message]
2013-08-19 13:45   ` Pedro Alves
2013-08-19 16:57     ` Luis Machado

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=520EF596.9020307@codesourcery.com \
    --to=lgustavo@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --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