Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Riccardo Murri <riccardo.murri@gmail.com>
Cc: emacs-devel@gnu.org, ding@gnus.org, xemacs-beta@xemacs.org
Subject: Re: Merge issues in `tls.el' (EMACS_22_BASE vs. trunk)
Date: Tue, 11 Mar 2008 08:28:52 +0900	[thread overview]
Message-ID: <b4m63vurwej.fsf@jpl.org> (raw)
In-Reply-To: <v93aqzt4p8.fsf@marauder.physik.uni-ulm.de>

>>>>> Reiner Steib wrote:
> On Mon, Mar 10 2008, Katsumi Yamaoka wrote:

>> In the Gnus v5-10 branch, which is being synch'd with the Emacs
>> EMACS_22_BASE branch, the version of tls.el that uses rx has been
>> merged yesterday.  And tls.el came not to be able to byte compile
>> with XEmacs, because rx.el is not available in XEmacs.  Could it
>> be rewritten not using rx.el?

> Yes, the version in Emacs trunk and Gnus trunk, the defcustom of
> `tls-end-of-info' has been rewritten not to use rx.  Please use this
> in v5-10.

Thanks.  I've imported the following change made in the Emacs trunk
(i.e., rdiff -r1.20 -r1.21) to the Gnus v5-10 branch.

2007-11-04  Glenn Morris  <rgm@gnu.org>

	* net/tls.el: Don't require rx when compiling.
	(tls-end-of-info): Rewrite without using rx.
	(open-tls-stream): Use with-current-buffer.

Regards,




      reply	other threads:[~2008-03-10 23:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <v94pbqrrt8.fsf@marauder.physik.uni-ulm.de>
     [not found] ` <13zltiauc8.fsf@fencepost.gnu.org>
     [not found]   ` <v9skz9jf1d.fsf@marauder.physik.uni-ulm.de>
     [not found]     ` <0vod9wblw1.fsf@fencepost.gnu.org>
2008-03-10  5:16       ` Katsumi Yamaoka
2008-03-10  7:32         ` Reiner Steib
2008-03-10 23:28           ` Katsumi Yamaoka [this message]

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=b4m63vurwej.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=riccardo.murri@gmail.com \
    --cc=xemacs-beta@xemacs.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. 
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 NNTP newsgroup(s).