From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Dave Abrahams <dave@boostpro.com>
Cc: ding@gnus.org
Subject: Re: [gnus git] branch master updated: m0-5-97-gafdb0e3 =6= Revert "Add recent argument to nnimap-find-article-by-message-id" ; Fix for macos keychain access ; gnus-try-warping-via-registry: [bugfix] don't act as though you've found the article when you haven't ; gnus-request-head: when gnus-override-method is set, allow the backend `request-head' function to determine the group name on its own. ; Change gnus-set-difference from O(N^2) to O(N) ; Filter out negative article numbers during expiry
Date: Fri, 31 Aug 2012 13:38:05 +0900 [thread overview]
Message-ID: <b4m8vcvn0b6.fsf@jpl.org> (raw)
In-Reply-To: <87ehmpqto6.fsf@dex.adm.naquadah.org>
Julien Danjou wrote:
> On Wed, Aug 29 2012, Dave Abrahams wrote:
>> - Log -----------------------------------------------------------------
>> commit afdb0e3005c7bc272b37602693eb24169fe9c0de
>> Author: Dave Abrahams <dave@boostpro.com>
>> Date: Tue Aug 28 12:34:49 2012 -0700
>>
>> Revert "Add recent argument to nnimap-find-article-by-message-id"
>>
>> This reverts commit ac8ce21091b89a7a05ad821854f4d3e7ff35a394.
>>
>> Conflicts:
>>
>> lisp/ChangeLog
>> lisp/nnimap.el
> I think you should at least modify the changelog file to add the fact
> that you reverted something, and explain why you did it.
> And all your others commits miss changelog entries too, as far as I can
> see.
Wasn't your change to nnimap.el incomplete? BTW, I've added change
log entries temporarily for the sake of synch'ng Emacs trunk with
Gnus master. Please fix wrong ones by yourself if any.
next prev parent reply other threads:[~2012-08-31 4:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1T6mSl-00057h-3s@quimby.gnus.org>
2012-08-29 21:23 ` Julien Danjou
2012-08-31 4:38 ` Katsumi Yamaoka [this message]
2012-08-31 6:36 ` Dave Abrahams
2012-08-31 14:34 ` Michael Welsh Duggan
2012-09-01 5:08 ` Dave Abrahams
2012-09-01 5:08 ` Dave Abrahams
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=b4m8vcvn0b6.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=dave@boostpro.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).