emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jay Kerns <gjkernsysu@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: ox-html.el removal
Date: Mon, 11 Mar 2013 09:57:31 -0400	[thread overview]
Message-ID: <CAFiLVraB+Uo+wmXRaSHem4v4Zb1m2B2Kz9DW7sJezQr8B7PEuw@mail.gmail.com> (raw)
In-Reply-To: <C559F53D-9A66-45C0-AF72-237F1E95D812@gmail.com>

Dear Carsten,

I certainly support your position.  And if *anybody's* wishes should
be honoured, I would think yours should be at the top of that list,
along with the wishes of the other (at least) 4 copyright holders' of
ox-html.el.

Cheers,
Jay



On Mon, Mar 11, 2013 at 4:58 AM, Carsten Dominik
<carsten.dominik@gmail.com> wrote:
>
> On 11.3.2013, at 05:08, Jambunathan K <kjambunathan@gmail.com> wrote:
>>
>> Even if my combative positioning doesn't amount to anything much, I want
>> to throw in a little friction by the way of Bastien and the current
>> release.  I am stating my purpose in no uncertain terms - yes it is to
>> delay the release or cause confusion.
>
> I don't think there is any confusion pertaining to the 8.0 release.  These files were brought into the Org-mode repository, marked as GPL from the start, so there are no formal issues including them in 8.0 in their current form.  Wether ox-odt.el should be moved to contrib as per Achims suggestion I don't know.   I would object moving ox-html.el, it contains a lot of variable definitions, documentation strings and code I and others wrote, even if you have made the interface with org-elemets.
>
> We will see in how far the FSF will follow your arguments and what will happen when we merge 8.0 into the Emacs distribution.  So I don't see a reason to hold up the 8.0 release.  With respect to Emacs, we will have time to resolve the issue one way or another.
>
> - Carsten

  reply	other threads:[~2013-03-11 13:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-10 15:22 ox-html.el removal Jambunathan K
2013-03-10 18:55 ` Detlef Steuer
2013-03-10 19:24   ` Andreas Röhler
2013-03-10 19:30   ` Christopher Schmidt
2013-03-10 20:37     ` Thomas S. Dye
2013-03-11  0:38     ` Alan L Tyree
2013-03-11  4:08     ` Jambunathan K
2013-03-11  5:39       ` Thomas S. Dye
2013-03-11  8:58       ` Carsten Dominik
2013-03-11 13:57         ` Jay Kerns [this message]
2013-03-11 15:55           ` Bastien
2013-03-11 17:33         ` Jambunathan K
2013-03-11 17:57           ` Eric Schulte
2013-03-11 20:11           ` T.F. Torrey
2013-03-11 22:32             ` Jonathan Leech-Pepin
2013-03-11  7:11 ` Achim Gratz
2013-03-11  8:11   ` Jay Kerns
2013-03-11 17:52     ` Jambunathan K
  -- strict thread matches above, loose matches on Subject: below --
2013-03-11 16:33 Rustom Mody

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=CAFiLVraB+Uo+wmXRaSHem4v4Zb1m2B2Kz9DW7sJezQr8B7PEuw@mail.gmail.com \
    --to=gjkernsysu@gmail.com \
    --cc=carsten.dominik@gmail.com \
    --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).