From: Eli Zaretskii <eliz@gnu.org>
To: stefan@marxist.se
Cc: 21103-done@debbugs.gnu.org, larsi@gnus.org, ansgar@43-1.org, rms@gnu.org
Subject: bug#21103: 24.5; LaTeX input mode: add more blackboard bold characters
Date: Fri, 31 Jan 2020 12:23:30 +0200 [thread overview]
Message-ID: <83ftfvlyal.fsf@gnu.org> (raw)
In-Reply-To: <83pnfcvfjg.fsf@gnu.org> (message from Eli Zaretskii on Tue, 21 Jan 2020 20:18:59 +0200)
> Date: Tue, 21 Jan 2020 20:18:59 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 21103@debbugs.gnu.org, larsi@gnus.org, ansgar@43-1.org
>
> > Given the above, I think this is fine to install with the
> > Copyright-paperwork-exempt tag.
> >
> > We could perhaps contact assign@gnu.org if we feel unsure about this,
> > to hear what they have to say. Does anyone think we should do that
> > first, or have any other comments? Otherwise, I think we should just
> > install it.
>
> Richard, are there any reasons to be more lenient with this kind of
> changes, wrt to the maximum number of lines we are allowed to accept
> without a copyright assignment? The original patch is here:
>
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=21103#5
>
> You can download the patch itself with this URL:
>
> https://debbugs.gnu.org/cgi/bugreport.cgi?msg=5;filename=0001-Add-more-blackboard-bold-characters.patch;att=1;bug=21103
Discussion with Richard indicated that such changes don't need any
copyright assignments, since they introduce code that is not
copyrightable. So I've pushed this to the emacs-27 branch, and I'm
closing the bug.
Thanks.
prev parent reply other threads:[~2020-01-31 10:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 11:28 bug#21103: 24.5; LaTeX input mode: add more blackboard bold characters Ansgar Burchardt
2016-02-23 9:37 ` Lars Ingebrigtsen
2020-01-20 20:41 ` Stefan Kangas
2020-01-21 18:18 ` Eli Zaretskii
2020-01-31 10:23 ` Eli Zaretskii [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=83ftfvlyal.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=21103-done@debbugs.gnu.org \
--cc=ansgar@43-1.org \
--cc=larsi@gnus.org \
--cc=rms@gnu.org \
--cc=stefan@marxist.se \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.