From: Fukuoka Daichi <dc-fukuoka@sgi.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: James Norris <jnorris@codesourcery.com>,
Thomas Schwinge <thomas@codesourcery.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: RE: [gomp4] Fix handling of subarrays with update directive
Date: Wed, 23 Mar 2016 11:31:00 -0000 [thread overview]
Message-ID: <328355B28C716D46ACDA3A24E0799BA1C19BDA5C@P-EXMB5-DC21.corp.sgi.com> (raw)
In-Reply-To: <20160323103709.GV3017@tucnak.redhat.com>
Jakub,
> The ChangeLog format is <date> <name> <surname> <email> thus company names aren't listed explicitly, but your email is @sgi.com, so it will be there.
I understand the format, thanks.
Regards,
Daichi Fukuoka
-----Original Message-----
From: Jakub Jelinek [mailto:jakub@redhat.com]
Sent: Wednesday, March 23, 2016 7:37 PM
To: Fukuoka Daichi
Cc: James Norris; Thomas Schwinge; GCC Patches
Subject: Re: [gomp4] Fix handling of subarrays with update directive
On Wed, Mar 23, 2016 at 10:31:33AM +0000, Fukuoka Daichi wrote:
> > Yeah, the oacc-mem.c is a two liner, we don't need copyright assignment for that, so please mention Daichi-san's name + mail address, and PR libgpmp/69414 in the ChangeLog entry.
>
> If possible, could you add " SGI Japan, Ltd." before/after my name?
> Because I am belonging to the company.
The ChangeLog format is <date> <name> <surname> <email> thus company names aren't listed explicitly, but your email is @sgi.com, so it will be there.
Jakub
next prev parent reply other threads:[~2016-03-23 11:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <56A0E84A.5030107@mentor.com>
[not found] ` <56F13A4E.20907@mentor.com>
2016-01-22 18:50 ` James Norris
2016-03-23 8:43 ` Thomas Schwinge
2016-03-23 10:33 ` Jakub Jelinek
2016-03-23 10:37 ` Fukuoka Daichi
2016-03-23 11:10 ` Jakub Jelinek
2016-03-23 11:31 ` Fukuoka Daichi [this message]
2016-03-23 13:15 ` James Norris
2016-03-23 13:18 ` Jakub Jelinek
2016-04-07 11:29 ` [gcc-5] " Thomas Schwinge
2016-04-07 11:30 ` Jakub Jelinek
2016-04-07 11:48 ` Thomas Schwinge
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=328355B28C716D46ACDA3A24E0799BA1C19BDA5C@P-EXMB5-DC21.corp.sgi.com \
--to=dc-fukuoka@sgi.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jnorris@codesourcery.com \
--cc=thomas@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).