From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Abhijit Halder <abhijit.k.halder@gmail.com>
Cc: Mike Frysinger <vapier@gentoo.org>,
Tom Tromey <tromey@redhat.com>,
gdb-patches@sourceware.org
Subject: Re: PATCH
Date: Wed, 20 Jul 2011 19:25:00 -0000 [thread overview]
Message-ID: <m3hb6gg5h9.fsf@redhat.com> (raw)
In-Reply-To: <CAOhZP9wFida5yEsH3s-_QzHLoUR0L6=D4fkLyFF8C5ecfzrpqA@mail.gmail.com> (Abhijit Halder's message of "Fri, 15 Jul 2011 12:04:49 +0530")
Abhijit Halder <abhijit.k.halder@gmail.com> writes:
> I have made the changes to handle following cases. Should I re-submit
> the new patch in the same thread, or I change the subject line (as it
> does not reveal much the problem definition) and re-submit the patch
> in a new thread?
Hello Abhijit,
As Tom said, either way is fine. Also, please don't do top-posting when
replying e-mails, i.e., don't reply on top of the other messages. We
prefer this style:
http://en.wikipedia.org/wiki/Posting_style#Interleaved_style
Please use it when you are replying to mailing lists in general.
Thank you.
next prev parent reply other threads:[~2011-07-20 18:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-09 13:09 PATCH Abhijit Halder
2011-07-09 19:06 ` PATCH oza Pawandeep
2011-07-11 12:13 ` PATCH Abhijit Halder
2011-07-11 13:42 ` PATCH Abhijit Halder
2011-07-10 7:47 ` PATCH Mike Frysinger
2011-07-11 21:10 ` PATCH Tom Tromey
2011-07-12 0:51 ` PATCH Abhijit Halder
2011-07-12 7:15 ` PATCH Abhijit Halder
2011-07-12 8:34 ` PATCH Mike Frysinger
2011-07-12 9:01 ` PATCH Abhijit Halder
2011-07-12 17:31 ` PATCH Mike Frysinger
2011-07-12 17:49 ` PATCH Matt Rice
2011-07-12 19:25 ` PATCH Mike Frysinger
2011-07-12 19:49 ` PATCH Tom Tromey
2011-07-12 20:43 ` PATCH Mike Frysinger
2011-07-13 8:45 ` PATCH Abhijit Halder
2011-07-15 14:15 ` PATCH Abhijit Halder
2011-07-15 20:49 ` PATCH Tom Tromey
2011-07-20 19:25 ` Sergio Durigan Junior [this message]
2011-07-21 11:08 ` gdb output pipelining to shell (was: Re: PATCH) Pedro Alves
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=m3hb6gg5h9.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=abhijit.k.halder@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
--cc=vapier@gentoo.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