Gnus development mailing list
 help / color / mirror / Atom feed
From: Miles Bader <miles.bader@necel.com>
To: ding@gnus.org
Subject: Re: Synch'ing with Emacs trunk
Date: Thu, 02 Oct 2008 14:45:16 +0900	[thread overview]
Message-ID: <buobpy31rf7.fsf@dhapc248.dev.necel.com> (raw)
In-Reply-To: <b4miqsc1w85.fsf@jpl.org>

Katsumi Yamaoka <yamaoka@jpl.org> writes:
> First of all, thanks for working on synch'ing Emacs and Gnus.
> But I was aware that some changes made in the Emacs trunk have
> not been merged in the Gnus trunk for three weeks, even though
> the changes made in Gnus have been merged in Emacs.  Currently
> they are in gnus-art.el, gnus-group.el, gnus-util.el, and mml.el
> AFAIK.  Is it intentional?

No, just laziness.  The Emacs->Gnus direction needs more manual cleanup
so I tend to do it less often.

I'll try to do it tonight.

-Miles

-- 
P.S.  All information contained in the above letter is false,
      for reasons of military security.




      reply	other threads:[~2008-10-02  5:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-01  9:49 Katsumi Yamaoka
2008-10-02  5:45 ` Miles Bader [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=buobpy31rf7.fsf@dhapc248.dev.necel.com \
    --to=miles.bader@necel.com \
    --cc=ding@gnus.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).