From: Christian Garbs <mitch@mitch.h.shuttle.de>
To: emacs-orgmode@gnu.org
Subject: Re: Babel support for Vala
Date: Thu, 13 Jul 2017 23:42:50 +0200 [thread overview]
Message-ID: <e7e12659-6e30-bcbf-8ad0-04d8dfff51cd@cgarbs.de> (raw)
In-Reply-To: <87vamztmvb.fsf@nicolasgoaziou.fr>
Hi,
Am 11.07.2017 um 10:10 schrieb Nicolas Goaziou:
> In the meantime, would you want to sent your library as a patch so that
> we can review it?
The patch is prepared but I have one question regarding the copyright
situation: Looking at the other files[1], I think I should now list the
FSF as copyright holder. Can I already do that before the paperwork has
been completed or do I have to hold the patch back until that time?
And should I send the patch as a reply into this thread or start a new one?
so long
Mitch
[1] `grep Copyright lisp/*.el' shows the FSF as copyright holder for all
files except `lisp/org-duration.el'. Is that a bug or intentional?
next prev parent reply other threads:[~2017-07-13 21:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-09 20:09 Babel support for Vala Christian Garbs
2017-07-10 9:03 ` Nicolas Goaziou
2017-07-10 17:54 ` Christian Garbs
2017-07-11 8:10 ` Nicolas Goaziou
2017-07-13 21:42 ` Christian Garbs [this message]
2017-07-14 8:30 ` Nicolas Goaziou
2017-07-14 19:43 ` [PATCH] ob-vala.el: Add Vala support to Babel Christian Garbs
2017-07-23 9:05 ` Nicolas Goaziou
2017-07-31 22:04 ` [PATCH v2] " Christian Garbs
2017-08-01 21:59 ` Nicolas Goaziou
2017-07-31 22:04 ` [PATCH v3] " Christian Garbs
2017-08-07 9:41 ` Nicolas Goaziou
2017-08-01 21:20 ` [PATCH] " Christian Garbs
2017-08-01 22:03 ` Nicolas Goaziou
2017-08-02 20:24 ` Christian Garbs
2017-08-03 10:49 ` Nicolas Goaziou
2017-08-05 19:53 ` Christian Garbs
2017-08-06 0:22 ` Nicolas Goaziou
2017-08-06 10:06 ` Christian Garbs
2017-08-07 9:52 ` Nicolas Goaziou
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e7e12659-6e30-bcbf-8ad0-04d8dfff51cd@cgarbs.de \
--to=mitch@mitch.h.shuttle.de \
--cc=emacs-orgmode@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/org-mode.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).