Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <teawater@gmail.com>
To: Jie Zhang <jie.zhang@analog.com>
Cc: tromey@redhat.com, Jie Zhang <jzhang918@gmail.com>,
	gdb-patches@sourceware.org,  	gdb@sourceware.org,
	Eli Zaretskii <eliz@gnu.org>
Subject: Re: [commit] Add myself to MAINTAINERS under Write After Approval  	(was Re: cvs-head "make install" get error with doc)
Date: Tue, 22 Sep 2009 04:01:00 -0000	[thread overview]
Message-ID: <daef60380909212100l5f827461re72bccbbbf6a600d@mail.gmail.com> (raw)
In-Reply-To: <4AB8441C.30700@analog.com>

Welcome to the club.

Hui

On Tue, Sep 22, 2009 at 11:27, Jie Zhang <jie.zhang@analog.com> wrote:
> Tom Tromey wrote:
>>>>>>>
>>>>>>> "Jie" == Jie Zhang <jzhang918@gmail.com> writes:
>>
>> Jie> And should or can I add myself to GDB MAINTAINERS under "Write After
>> Jie> Approval". My employer's copyright assignment should have already
>> Jie> covered me.
>>
>> Yes, if you have write access, you should be mentioned there.
>>
> Thanks. I have added myself with the attached patch.
>
> Jie
>


      reply	other threads:[~2009-09-22  4:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <daef60380909210004v50e5eafcl26e180d0e8b73482@mail.gmail.com>
2009-09-21  7:23 ` cvs-head "make install" get error with doc Jie Zhang
2009-09-21  7:31   ` Jie Zhang
     [not found]     ` <h97ov6$i7q$1@ger.gmane.org>
2009-09-21 12:51       ` Jie Zhang
2009-09-22  2:19         ` Hui Zhu
     [not found]   ` <4AB72BD8.5020606__48069.4626960487$1253518331$gmane$org@analog.com>
2009-09-21 16:56     ` Tom Tromey
2009-09-21 17:28       ` Jie Zhang
     [not found]       ` <6f48278f0909211028x66561a09wd74cebc5f95f832d__25635.7262297117$1253554143$gmane$org@mail.gmail.com>
2009-09-21 19:24         ` Tom Tromey
2009-09-22  3:27           ` [commit] Add myself to MAINTAINERS under Write After Approval (was Re: cvs-head "make install" get error with doc) Jie Zhang
2009-09-22  4:01             ` Hui Zhu [this message]

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=daef60380909212100l5f827461re72bccbbbf6a600d@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=gdb@sourceware.org \
    --cc=jie.zhang@analog.com \
    --cc=jzhang918@gmail.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