From: Eli Zaretskii <eliz@gnu.org>
To: joakim@verona.se
Cc: emacs-devel@gnu.org
Subject: Re: Merging the xwidget branch
Date: Fri, 11 Dec 2015 18:17:42 +0200 [thread overview]
Message-ID: <83oadx6jtl.fsf@gnu.org> (raw)
In-Reply-To: <m31tatf1a1.fsf@exodia.verona.se>
> From: joakim@verona.se
> Cc: emacs-devel@gnu.org
> Date: Fri, 11 Dec 2015 16:33:26 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > What's the status on this? Is anything preventing the merge?
>
> Status:
>
> - I think it can be applied to master, but there are some known cosmetic
> issues that can be presumably fixed afterwards
Right, this shouldn't hold us.
> - Nobody likes the xwidget name, so there was a discussion regarding
> renaming the feature. It feels better changing the name before
> applying the patch to master(or wherever it's supposed to
> go). However, no consensus has been reached on a name yet.
Let's leave this for later, I see no problem in mechanistic renaming.
> - I would like some hand-holding during commiting of the patch, better
> yet if some trusted party could do it for me with hand holding from me
> instead
What exactly are the problems you envision?
> - Some unforseen events have made me have less time than usual at the
> moment.
Will you be able to look into any problems that might come up after
the merge?
next prev parent reply other threads:[~2015-12-11 16:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 9:44 Merging the xwidget branch Eli Zaretskii
2015-12-11 15:33 ` joakim
2015-12-11 16:17 ` Eli Zaretskii [this message]
2015-12-11 16:33 ` joakim
2015-12-11 18:32 ` Eli Zaretskii
2016-01-09 9:52 ` joakim
2016-01-09 11:23 ` Eli Zaretskii
2016-01-11 17:55 ` John Wiegley
2016-01-11 19:00 ` Eli Zaretskii
2016-01-09 9:55 ` joakim
2016-01-11 19:34 ` Wolfgang Jenkner
2016-01-11 19:43 ` joakim
2016-01-16 8:27 ` Eli Zaretskii
2016-01-17 20:03 ` joakim
2016-01-17 20:49 ` Eli Zaretskii
2016-01-18 7:28 ` joakim
2016-01-18 15:39 ` Eli Zaretskii
2016-01-18 21:52 ` joakim
2016-01-19 15:53 ` Eli Zaretskii
2016-01-19 20:08 ` joakim
2016-01-19 20:22 ` Eli Zaretskii
2016-01-20 7:28 ` John Wiegley
2016-01-20 7:56 ` Nicolas Petton
2016-01-18 12:11 ` joakim
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=83oadx6jtl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=joakim@verona.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.