From: Ulf Jasper <ulf.jasper@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: master c5e8254 2/3: Apply icalendar.el patch by Thomas Plass <thunk2@arcor.de>. Fix bug#34315.
Date: Wed, 02 Sep 2020 20:24:52 +0200 [thread overview]
Message-ID: <87y2lsdojv.fsf@panama> (raw)
In-Reply-To: <83tuwgujyk.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 02 Sep 2020 21:12:03 +0300")
Am 02.09.2020 um 21:12 (+0300) schrieb Eli Zaretskii:
> Please in the future, when you commit patches by someone else, make
> them the author of the commit, instead of just mentioning their names
> in the log message. If the patch was not formatted by the likes of
> "git format-patch", you can use Git's --author switch (or any
> equivalent feature) to specify the actual author at commit time.
>
> Also, Thomas doesn't seem to have a copyright assignment on file,
> which means we can only accept small contributions from him (and this
> one is already slightly larger than the limit), and those
> contributions must be marked with
>
> Copyright-paperwork-exempt: yes
>
> in the log message.
>
> Please make a point of observing these rules in the future, they are
> important to allow us maintain correct attributions for the code we
> accept, and know their legal status. When in doubt, please ask here.
Sorry for breaking the rules. Will do better next time.
I have somee questions though:
- Who is allowed to proclaim a Copyright-paperwork-exemption?
- What is the limit? (I checked 'CONTRIBUTE' before committing but did
not find one. (Maybe I just missed it.) So I assumed this patch to
be "small".)
- Does it matter that I modified the patch before committing and
pushing?
next prev parent reply other threads:[~2020-09-02 18:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 18:12 master c5e8254 2/3: Apply icalendar.el patch by Thomas Plass <thunk2@arcor.de>. Fix bug#34315 Eli Zaretskii
2020-09-02 18:24 ` Ulf Jasper [this message]
2020-09-02 18:36 ` Eli Zaretskii
2020-09-02 18:54 ` Ulf Jasper
2020-09-02 18:58 ` Eli Zaretskii
2020-09-02 19:21 ` Ulf Jasper
2020-09-03 13:07 ` Eli Zaretskii
2020-09-03 14:31 ` Ulf Jasper
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y2lsdojv.fsf@panama \
--to=ulf.jasper@web.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).