Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Remove unused variable
Date: Mon, 21 Apr 2014 17:14:00 -0000	[thread overview]
Message-ID: <20140421171453.GA18355@adacore.com> (raw)
In-Reply-To: <53554D62.2010901@ericsson.com>

> >> 2014-04-21  Simon Marchi <simon.marchi@ericsson.com>
> >>
> >> 	* infrun.c (resume): Remove should_resume (unused).
> > 
> > Unfortunately, your patch does much much much much much much much
> > more than just removing "should_resume" :-).
> > 
> > Can you please submit a patch that just removes that variable?
> 
> I was afraid it would not be clear and I almost mentioned it in my
> original message. There are a lot of +/- for a tiny change, because the
> code looked like that:
> 
> int should_resume = 1;
> 
> /* Untouched stuff */
> 
> if (should_resume)
>   {
>     /* Lots of stuff that needs to be unindented. */
>     ...
>   }
> 
> The part that was unindented by four spaces generates a lot of +/-, but
> I didn't change anything else than that, I swear !

Indeed. It went a little too fast - what threw me was the addition
of resume_ptid's declaration at the start of the function. I did
a quick "git diff -b" and it explains the patch.

The patch is approved, but we should probably mention the fact that
resume_ptid's declaration was moved up in the ChangeLog entry.

Here is a link to request an account on sourceware.org, if you do not
already have one (you can list me as your sponsor):
https://sourceware.org/cgi-bin/pdw/ps_form.cgi

Once that's out of the way, please commit an obvious patch to
the gdb/MAINTAINERS file adding yourself to the "COMMIT AFTER
APPROVAL" list (the patch should be treated like all other obvious
patches, ie a copy should be sent to this mailing-list). Once that's
all done, then you can push this commit as well. Please remember
to send a quick confirmation that the commit was pushed to this
mailing-list as well.

Thank you,
-- 
Joel


  reply	other threads:[~2014-04-21 17:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-21 15:49 Simon Marchi
2014-04-21 16:12 ` Joel Brobecker
2014-04-21 16:54   ` Simon Marchi
2014-04-21 17:14     ` Joel Brobecker [this message]
2014-04-21 17:36       ` Simon Marchi
2014-04-21 17:47         ` Joel Brobecker
2014-05-13 20:55       ` Simon Marchi

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=20140421171453.GA18355@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@ericsson.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