Gnus development mailing list
 help / color / mirror / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: ding@gnus.org
Cc: emacs-devel@gnu.org
Subject: syncing from Emacs to Gnus [was Re: declare-function in files from Gnus (hashcash.el, imap.el)]
Date: Sat, 01 Dec 2007 16:42:41 -0500	[thread overview]
Message-ID: <y3tzn2148e.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <v9tzn3bav9.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Fri, 30 Nov 2007 23:56:58 +0100")

Reiner Steib wrote:

> I think the following changes...
>
> 	* mail/hashcash.el (message-narrow-to-headers-or-head)
> 	* net/imap.el (sasl-find-mechanism, sasl-mechanism-name)
[...]
> ... will break compatibility of Gnus with Emacs 21, Emacs 22.1 and
> XEmacs when synced to Gnus repository (doesn't happen immediately,
> because Miles is on a trip).  

Perhaps you only want to sync the files from the lisp/gnus directory
in Emacs to Gnus? In other words, stop syncing files once they get
moved out of the gnus/ directory? Have a static "contrib" directory in
Gnus, or something, that provides the files if they are not already in
the Emacs distribution... Just an idea.

  parent reply	other threads:[~2007-12-01 21:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-30 22:56 declare-function in files from Gnus (hashcash.el, imap.el) Reiner Steib
2007-11-30 23:27 ` Glenn Morris
2007-12-01 18:35   ` Reiner Steib
2007-12-01 18:54     ` Dan Nicolaescu
2007-12-01 20:35       ` Glenn Morris
2007-12-01 20:40         ` Dan Nicolaescu
2007-12-01 21:50     ` Glenn Morris
2007-12-01 21:42 ` Glenn Morris [this message]
2007-12-01 23:22   ` syncing from Emacs to Gnus Reiner Steib
2007-12-02 14:56     ` Stefan Monnier
2007-12-02 18:39     ` Richard Stallman
2007-12-03  2:25       ` Stefan Monnier
2007-12-03 18:43         ` Richard Stallman
2007-12-03 18:59           ` Stefan Monnier
2007-12-06  2:12             ` Richard Stallman
     [not found] ` <fir8np$3br$1@ger.gmane.org>
     [not found]   ` <200712011634.lB1GYCkr018222@oogie-boogie.ics.uci.edu>
     [not found]     ` <87mysuwdcx.fsf@neutrino.caeruleus.net>
     [not found]       ` <E1IybxG-0000AT-DD@fencepost.gnu.org>
     [not found]         ` <87ac27w4lz.fsf@neutrino.caeruleus.net>
     [not found]           ` <E1IywKa-0006WN-2v@fencepost.gnu.org>
     [not found]             ` <87u00eufga.fsf@neutrino.caeruleus.net>
     [not found]               ` <200712022237.lB2MbNC8016800@oogie-boogie.ics.uci.edu>
     [not found]                 ` <v9d4tnxtiw.fsf@marauder.physik.uni-ulm.de>
     [not found]                   ` <200712032340.lB3Ne3Vt009200@oogie-boogie.ics.uci.edu>
2007-12-05 20:35                     ` declare-function in files from Gnus (hashcash.el, imap.el) Reiner Steib
2007-12-05 21:01                       ` Glenn Morris
2007-12-08 19:42                         ` Reiner Steib
2007-12-08 22:58                           ` Dan Nicolaescu
2007-12-09  2:20                             ` Glenn Morris
2007-12-09 20:10                               ` Austin Frank
2007-12-09 21:22                                 ` Reiner Steib

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=y3tzn2148e.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.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).