unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex Harsanyi <alexharsanyi@gmail.com>
To: Thomas Fitzsimmons <fitzsim@fitzsim.org>
Cc: Noam Postavsky <npostavs@gmail.com>, 31742-done@debbugs.gnu.org
Subject: bug#31742: 26.1.50; excorporate.elc byte-compiled in Emacs 25.x fails in Emacs 26.1
Date: Sun, 17 Jun 2018 08:12:19 +0800	[thread overview]
Message-ID: <CAH-ciFpWbcTsEVR1vqReqD2YnfZHnp99rybR16u-m_qhxn=KJQ@mail.gmail.com> (raw)
In-Reply-To: <m3muw022fv.fsf@fitzsim.org>

On Tue, Jun 12, 2018 at 9:55 AM, Thomas Fitzsimmons <fitzsim@fitzsim.org> wrote:

> I added the comment, bumped the soap-client version to 3.1.4 and pushed
> the patch to master so that GNU ELPA will be regenerated tonight.  I
> also backported the patch to the emacs-26 branch since it fixes a
> functional regression.

Hi Thomas,

Can you let me know where did you push the soap-client changes?

I can see that the package was released at gnu.elpa.org, but the
changes were not pushed either to the elpa.git repository at
https://git.savannah.gnu.org/git/emacs/elpa.git, or to my own copy of
it at https://github.com/alex-hhh/emacs-soap-client.

Thanks,
Alex.

>
> Thomas





  parent reply	other threads:[~2018-06-17  0:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-07  1:07 bug#31742: 26.1.50; excorporate.elc byte-compiled in Emacs 25.x fails in Emacs 26.1 Thomas Fitzsimmons
2018-06-07  1:14 ` Noam Postavsky
2018-06-07  2:01   ` Thomas Fitzsimmons
2018-06-07 12:21     ` Noam Postavsky
2018-06-07 14:06       ` Thomas Fitzsimmons
2018-06-07 17:36         ` Noam Postavsky
2018-06-08  1:13           ` Thomas Fitzsimmons
2018-06-08  1:57             ` Noam Postavsky
2018-06-08  2:17               ` Thomas Fitzsimmons
2018-06-08 12:19                 ` Noam Postavsky
2018-06-08 14:18                   ` Thomas Fitzsimmons
2018-06-09  0:01                     ` Alex Harsanyi
2018-06-09  2:54                       ` Thomas Fitzsimmons
2018-06-09  9:13                         ` Alex Harsanyi
2018-06-09 10:32                           ` Thomas Fitzsimmons
2018-06-12  1:55                           ` Thomas Fitzsimmons
2018-06-12 17:11                             ` Eli Zaretskii
2018-06-13  1:39                               ` Thomas Fitzsimmons
2018-06-17  0:12                             ` Alex Harsanyi [this message]
2018-06-17  0:36                               ` Thomas Fitzsimmons
2018-06-17  1:31                                 ` Alex Harsanyi
2018-06-17  1:36                                   ` Noam Postavsky
2018-06-17 13:02                                   ` Thomas Fitzsimmons
2018-06-09 10:30                       ` Thomas Fitzsimmons
2018-06-09 12:13                         ` Noam Postavsky

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='CAH-ciFpWbcTsEVR1vqReqD2YnfZHnp99rybR16u-m_qhxn=KJQ@mail.gmail.com' \
    --to=alexharsanyi@gmail.com \
    --cc=31742-done@debbugs.gnu.org \
    --cc=fitzsim@fitzsim.org \
    --cc=npostavs@gmail.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).