Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: Just a bit confused about following gnus devel branch
Date: Mon, 06 Feb 2012 10:34:18 +0900	[thread overview]
Message-ID: <b4maa4wwxr9.fsf@jpl.org> (raw)
In-Reply-To: <87ehu9c9fv.fsf@gmail.com>

antoine.levitt@gmail.com wrote:

AFAIU, and what I'm doing is:

> What about synchronisation with emacs?
> Does emacs track nognus?

Emacs trunk and Gnus no-gnus branch are being synchronized now.

> Will it continue doing so after feature freeze?

I'm going to make Emacs trunk and Gnus trunk (Ma gnus) get synch'd
after Emacs 24.1 release.

> Do I have to track gnus specifically in addition to emacs to benefit
> from the latest features?



  reply	other threads:[~2012-02-06  1:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-05 13:17 Harry Putnam
2012-02-05 14:23 ` Ted Zlatanov
2012-02-05 14:40   ` Harry Putnam
2012-02-05 16:26     ` Tassilo Horn
2012-02-09 14:01       ` Harry Putnam
2012-02-09 14:09         ` Tassilo Horn
2012-02-05 15:28   ` Richard Riley
2012-02-06  3:57     ` Dave Goldberg
2012-02-05 20:27   ` Antoine Levitt
2012-02-06  1:34     ` Katsumi Yamaoka [this message]
2012-02-06  6:34 ` Steinar Bang

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=b4maa4wwxr9.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --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).