From: Eli Zaretskii <eliz@gnu.org>
To: Protesilaos Stavrou <info@protesilaos.com>
Cc: stefan@marxist.se, 43019@debbugs.gnu.org
Subject: bug#43019: Bundle modus-operandi-theme and modus-vivendi-theme with Emacs
Date: Mon, 24 Aug 2020 15:09:02 +0300 [thread overview]
Message-ID: <837dto6yap.fsf@gnu.org> (raw)
In-Reply-To: <87o8n0xnbx.fsf@protesilaos.com> (message from Protesilaos Stavrou on Mon, 24 Aug 2020 15:03:46 +0300)
> From: Protesilaos Stavrou <info@protesilaos.com>
> Cc: Stefan Kangas <stefan@marxist.se>, 43019@debbugs.gnu.org
> Date: Mon, 24 Aug 2020 15:03:46 +0300
>
> > There should be no problem adding this to Emacs, but the author needs
> > to explicitly say he donates the code to Emacs.
>
> I am fine with contributing them to Emacs. Thanks! Do I need to sign
> some extra paper or something?
No, I think this email message is enough. Thanks.
> In technical terms, how would this affect their development? Do I need
> to change their git repo to some other source? How will new
> commits/releases be synced with Emacs? Would development be shared with
> emacs-devel or some other mailing list?
From my POV, the ideal arrangement would be for you to tell us when to
sync the version in Emacs, or maybe even push the changes yourself.
> Sorry for the questions: I am just fairly new to this.
No need to apologize, the questions are all well taken.
next prev parent reply other threads:[~2020-08-24 12:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 11:33 bug#43019: Bundle modus-operandi-theme and modus-vivendi-theme with Emacs Stefan Kangas
2020-08-24 11:47 ` Eli Zaretskii
2020-08-24 12:03 ` Protesilaos Stavrou
2020-08-24 12:09 ` Eli Zaretskii [this message]
2020-08-24 13:13 ` Stefan Kangas
2020-08-24 13:34 ` Eli Zaretskii
2020-08-24 13:53 ` Stefan Kangas
2020-08-24 15:44 ` Protesilaos Stavrou
2020-08-25 14:21 ` Stefan Kangas
2020-08-26 22:28 ` Protesilaos Stavrou
2020-08-26 23:52 ` Stefan Kangas
2020-08-25 12:33 ` Stefan Kangas
2020-08-25 13:06 ` Eli Zaretskii
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=837dto6yap.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=43019@debbugs.gnu.org \
--cc=info@protesilaos.com \
--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.