Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: oza Pawandeep <oza.pawandeep@gmail.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: [FYI] write-after-apporval commit
Date: Mon, 26 Mar 2012 18:27:00 -0000	[thread overview]
Message-ID: <CAK1A=4xa=kFBRmuTznvdRD-RgA7ENg6G1o4PEXvRK=9-2-mjOg@mail.gmail.com> (raw)

Hi All,

please find the write-after-approval FYI below.

diff -urN old/ChangeLog new/ChangeLog
--- old/ChangeLog       2012-03-26 23:54:53.000000000 +0530
+++ new/ChangeLog       2012-03-26 23:54:21.000000000 +0530
@@ -1,3 +1,7 @@
+2012-03-26 Oza Pawandeep  <oza.pawandeep@gmail.com>
+
+        * MAINTAINERS (Write After Approval): Add myself to the list.
+
 2012-03-25  Jan Kratochvil  <jan.kratochvil@redhat.com>

        * NEWS (set breakpoint condition-evaluation): Change "gdb" to "host".
diff -urN old/MAINTAINERS new/MAINTAINERS
--- old/MAINTAINERS     2012-03-26 23:55:04.000000000 +0530
+++ new/MAINTAINERS     2012-03-26 23:54:28.000000000 +0530
@@ -649,6 +649,7 @@
 Wu Zhou                                                woodzltc@cn.ibm.com
 Yoshinori Sato                                 ysato@users.sourceforge.jp
 Hui Zhu                                                teawater@gmail.com
+Oza Pawandeep                                  oza.pawandeep@gmail.com

                        Past Maintainers


Regards,
Oza.


             reply	other threads:[~2012-03-26 18:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-26 18:27 oza Pawandeep [this message]
2012-03-27 17:07 ` Jan Kratochvil
2012-03-27 18:58   ` oza Pawandeep
2012-03-27 19:01     ` Jan Kratochvil
2012-03-28  3:58       ` oza Pawandeep
2012-03-28  4:35         ` oza Pawandeep
2012-03-28  5:08           ` Jan Kratochvil

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='CAK1A=4xa=kFBRmuTznvdRD-RgA7ENg6G1o4PEXvRK=9-2-mjOg@mail.gmail.com' \
    --to=oza.pawandeep@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