Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: pending patches
Date: Tue, 02 Jul 2013 19:39:59 +0900	[thread overview]
Message-ID: <b4mli5pjlds.fsf@jpl.org> (raw)
In-Reply-To: <8761wt5wmm.fsf@randomsample.de>

David Engster wrote:
> Katsumi Yamaoka writes:
>> I am a sync engineer merging changes made in Emacs and Gnus one
>> another, and have patches[1] that haven't been applied to Emacs
>> yet left on the shelf.  AFAIU, why it is pending is that there
>> are some unresolved problems[2].  Unfortunately the majority of
>> the changes are for IMAP and I'm not an IMAP user, so I'm not
>> capable to join in the development.  Now let me make a question;
>> what do you think a better way to handle them?
>>
>> 1. Keep the diffs (forever?)
>> 2. Merge the diffs to Emacs, to open to many users/developers.
>> 3. Revert the diffs.
>>
>> +1 to 2. :)

> I'd also say go ahead and merge them. Besides the repeated 'initial
> sync's (which however should be fixed now), I haven't seen any problems
> regarding unexist tracking anymore. I am however using Dovecot, which is
> a pretty sane IMAP implementation compared to say, GMail or Zimbra, so
> people using those might have other experiences. Still, the next Emacs
> release is still quite far away, so there's ample time for fixing
> things.

Thanks Ted and David.  I believe there's no one who wants to make
it regress, so I've done it.



      reply	other threads:[~2013-07-02 10:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-01 11:14 Katsumi Yamaoka
2013-07-01 12:33 ` Ted Zlatanov
2013-07-02  6:00 ` David Engster
2013-07-02 10:39   ` 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=b4mli5pjlds.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).