From: Mohamed Atef <mohamedatef1698@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] libgompd: Add OMPD support and global ICV functions
Date: Wed, 18 May 2022 15:06:49 +0200 [thread overview]
Message-ID: <CAPFh8NKh06zTUdRf3AR18mTYtQOQrQBdkzfvO9Lkc9mfwpMUow@mail.gmail.com> (raw)
In-Reply-To: <CAPFh8NKfx=1Jp9yf8bSVdFNw4ybZin19OHruk3rZk_vp6FG73A@mail.gmail.com>
Hi Jakub,
Sorry for the rush of emails, I removed the Copyright part, I will use
DCO.
Note: I filled out the form.
On Wed, May 18, 2022 at 2:55 PM Mohamed Atef <mohamedatef1698@gmail.com>
wrote:
>
>
> On Wed, May 18, 2022 at 2:43 PM Jakub Jelinek <jakub@redhat.com> wrote:
>
>> On Wed, May 18, 2022 at 02:10:29PM +0200, Mohamed Atef wrote:
>> > > As I said earlier, as this is just partial implementation of the
>> > > OMPD, I think it would be better to commit it to a git branch but
>> > > already in the upstream repository, say devel/omp/ompd branch.
>> > >
>> > > Do you have a FSF Copyright assignment on file or do you want to
>> > > submit this under DCO (https://gcc.gnu.org/dco.html)?
>> >
>> > If the latter, should I remove the header comment?
>> > I mean this part " Copyright (C) 2022 Free Software Foundation, Inc.
>> > Contributed by Mohamed Atef <mohamedatef1698@gmail.com>.
>> "
>> > In fact, I don't know the difference, so which is better for the
>> community?
>>
>
> Getting the FSF Copyright assignment can take a while, in the past it
>> involved sending snail mail papers and could take a few weeks or more,
>> I think nowadays it is through email but still can take some time.
>> The DCO is described in the link above.
>>
>> As for the Copyright line, I must say I don't know,
>> https://gcc.gnu.org/pipermail/gcc/2021-June/236217.html
>> says that it probably should be just
>> Copyright The GNU Toolchain Authors.
>>
> I don't have FSF Copyright, I just copied the comment as I thought it's
> some standard.
> I will change it to "Copyright The GNU Toolchain Authors".
>
>> in that case, but we have the DCO option only for less than a year
>> and apparently no file has such a Copyright line.
>>
>> If you wish to use FSF Copyright assignment, somebody needs to mail you
>> details that you fill in and mail to FSF.
>>
>> I will use DCO, we have less than 2 months to finish the project.
>
>> Jakub
>>
> Mohamed
>
prev parent reply other threads:[~2022-05-18 13:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 17:35 Mohamed Atef
2022-05-18 7:34 ` Jakub Jelinek
2022-05-18 12:10 ` Mohamed Atef
2022-05-18 12:41 ` Mohamed Atef
2022-05-18 12:43 ` Jakub Jelinek
2022-05-18 12:55 ` Mohamed Atef
2022-05-18 13:06 ` Mohamed Atef [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=CAPFh8NKh06zTUdRf3AR18mTYtQOQrQBdkzfvO9Lkc9mfwpMUow@mail.gmail.com \
--to=mohamedatef1698@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).