unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Mauger <mmauger@protonmail.com>
To: larsi@gnus.org, carlosjosepita@gmail.com
Cc: michael@mauger.com, 32724@debbugs.gnu.org
Subject: bug#32724: 26.1; sql.el: support presto client
Date: Wed, 26 Jun 2019 03:15:43 +0000	[thread overview]
Message-ID: <VXHkzf4OzZsso9e8xpTBtm5naUzJvr62HJ0WqUaGAmv9OBs0LqnLYUMiHjPeaK-1NNYeRxyf89q3V20dHKRjjYMf8DBX6yAQc5rvImfoML8=@protonmail.com> (raw)
In-Reply-To: <m3y31synrl.fsf@gnus.org>

[-- Attachment #1: Type: text/plain, Size: 967 bytes --]

-------- Original Message --------
> On Jun 23, 2019, 5:50 PM, Lars Ingebrigtsen < larsi@gnus.org> wrote:
> Carlos Pita <carlosjosepita@gmail.com> writes:
> > Here is a tentative partial implementation:
> >
> > ...
> I've Cc'd Michael Mauger on this -- perhaps he has a comment.

I'm sorry, I thought I had already responded to this on debbugs already...

My recommendation is to implement this as an ELPA package. That way it can be on a more frequent release cycle than core Emacs, and it gives you and others more leeway to provide more workflow features tailored specifically to Presto.

You've gone to this much effort.
You are going to have to assign your copyright to the FSF if the code is included in sql.el or in an ELPA module.
Come join us and become a package maintainer. I can certainly provide some guidance, but you've got a solid starting point.

Come join the Free side! :)

-- MICHAEL@MAUGER.COM // FSF and EFF member // GNU Emacs sql.el maintainer

[-- Attachment #2: Type: text/html, Size: 1078 bytes --]

  reply	other threads:[~2019-06-26  3:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-12 17:08 bug#32724: 26.1; sql.el: support presto client Carlos Pita
2019-06-23 21:50 ` Lars Ingebrigtsen
2019-06-26  3:15   ` Michael Mauger [this message]
2019-06-26 11:02     ` Lars Ingebrigtsen

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='VXHkzf4OzZsso9e8xpTBtm5naUzJvr62HJ0WqUaGAmv9OBs0LqnLYUMiHjPeaK-1NNYeRxyf89q3V20dHKRjjYMf8DBX6yAQc5rvImfoML8=@protonmail.com' \
    --to=mmauger@protonmail.com \
    --cc=32724@debbugs.gnu.org \
    --cc=carlosjosepita@gmail.com \
    --cc=larsi@gnus.org \
    --cc=michael@mauger.com \
    /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).