Gnus development mailing list
 help / color / mirror / Atom feed
* Re: Merge issues in `tls.el' (EMACS_22_BASE vs. trunk)
       [not found]     ` <0vod9wblw1.fsf@fencepost.gnu.org>
@ 2008-03-10  5:16       ` Katsumi Yamaoka
  2008-03-10  7:32         ` Reiner Steib
  0 siblings, 1 reply; 3+ messages in thread
From: Katsumi Yamaoka @ 2008-03-10  5:16 UTC (permalink / raw)
  To: Riccardo Murri; +Cc: xemacs-beta, ding, emacs-devel

> Reiner Steib wrote:

>> The "problem" is loading rx and (maybe more important) unnecessary
>> differences between branch and trunk.

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?

(info "(gnus)Emacsen")
,----
| Gnus should work on:
|
|    * Emacs 21.1 and up.
|
|    * XEmacs 21.4 and up.
`----

Regards,




^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Merge issues in `tls.el' (EMACS_22_BASE vs. trunk)
  2008-03-10  5:16       ` Merge issues in `tls.el' (EMACS_22_BASE vs. trunk) Katsumi Yamaoka
@ 2008-03-10  7:32         ` Reiner Steib
  2008-03-10 23:28           ` Katsumi Yamaoka
  0 siblings, 1 reply; 3+ messages in thread
From: Reiner Steib @ 2008-03-10  7:32 UTC (permalink / raw)
  To: Katsumi Yamaoka; +Cc: Riccardo Murri, emacs-devel, ding, xemacs-beta

On Mon, Mar 10 2008, Katsumi Yamaoka wrote:

>> Reiner Steib wrote:
>>> The "problem" is loading rx and (maybe more important) unnecessary
>>> differences between branch and trunk.
>
> 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.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/




^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Merge issues in `tls.el' (EMACS_22_BASE vs. trunk)
  2008-03-10  7:32         ` Reiner Steib
@ 2008-03-10 23:28           ` Katsumi Yamaoka
  0 siblings, 0 replies; 3+ messages in thread
From: Katsumi Yamaoka @ 2008-03-10 23:28 UTC (permalink / raw)
  To: Riccardo Murri; +Cc: emacs-devel, ding, xemacs-beta

>>>>> 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,




^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2008-03-10 23:28 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [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       ` Merge issues in `tls.el' (EMACS_22_BASE vs. trunk) Katsumi Yamaoka
2008-03-10  7:32         ` Reiner Steib
2008-03-10 23:28           ` Katsumi Yamaoka

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).