Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Abhijit Halder <abhijit.k.halder@gmail.com>
Subject: Re: [PATCH] [PR 9514] Fixing parse error for "pointer to a function pointer"
Date: Thu, 29 Sep 2011 11:13:00 -0000	[thread overview]
Message-ID: <201109291210.01022.pedro@codesourcery.com> (raw)
In-Reply-To: <CAOhZP9yqbRXOd6rP2v1mpjszvRhycAOP9JwJXa+SQNz7tF5BRQ@mail.gmail.com>

On Thursday 29 September 2011 11:44:04, Abhijit Halder wrote:
> On Thu, Sep 29, 2011 at 4:10 PM, Abhijit Halder
> <abhijit.k.halder@gmail.com> wrote:
> > Hi all,
> >
> > The current patch is to fix the issue defined in PR 9514. There's no
> > regression. Please review this.
> >
> > Thanks,
> > Abhijit Halder
> >
> 
> Oops! The ChangeLog is incorrect. Correcting the same.

Please always post both ChangeLog and patch together.  It's
practically 0 work to repost the whole thing instead of just a
part, while having all pieces together is easier for review, as
it avoids the reviewer, not being as familiar with the patches
as you, having to hunt for the pieces.  Also, please always try
to give explanations of what was wrong in the current code, and how
you're fixing the problem.  If you found a problem with an earlier
patch attempt, it's quite useful to know why that earlier patch didn't
work.  If a reviewer will need to try out a patch and go through
the same debug/thought process you had to go throught when writting
the patch, then it's more likely a patch will go by unreviewed
for longer.  In a nutshell, your job is to make it easy to get an OK.

-- 
Pedro Alves


  reply	other threads:[~2011-09-29 11:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-29 10:44 Abhijit Halder
2011-09-29 10:51 ` Abhijit Halder
2011-09-29 11:13   ` Pedro Alves [this message]
2011-09-29 11:49     ` Abhijit Halder
2011-10-03 16:46       ` Tom Tromey
2011-10-06 21:09         ` Keith Seitz
2011-10-17 11:16           ` Abhijit Halder
2011-10-18 20:14             ` Keith Seitz
2011-10-18 20:51               ` Tom Tromey

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=201109291210.01022.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=abhijit.k.halder@gmail.com \
    --cc=gdb-patches@sourceware.org \
    /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