From: Greg Troxel <gdt@work.lexort.com>
To: Julien Danjou <julien@danjou.info>
Cc: ding@gnus.org
Subject: Re: recent imap regression
Date: Mon, 06 Aug 2012 09:11:11 -0400 [thread overview]
Message-ID: <smu628wdv2o.fsf@linuxpal.mit.edu> (raw)
In-Reply-To: <87ipcwyznf.fsf@dex.adm.naquadah.org> (Julien Danjou's message of "Mon, 06 Aug 2012 14:26:44 +0200")
[-- Attachment #1: Type: text/plain, Size: 523 bytes --]
Julien Danjou <julien@danjou.info> writes:
> On Mon, Aug 06 2012, Greg Troxel wrote:
>
>> I just updated to latest git, and it looks like these two changes:
>>
>> b12f45e int, nnimap: remove to-buffer in request-head
>> 04ef222 gnus-int: add to-buffer parameter to gnus-request-head
>>
>> which were intended to be a change and a revert, ended up doing:
>
> Yep, already fixed.
Thanks. It might be good to use 'git revert' to undo things, since it's
guaranteed (absent merge conflicts) to apply inverse changesets.
[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2012-08-06 13:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-06 12:00 Greg Troxel
2012-08-06 12:26 ` Julien Danjou
2012-08-06 13:11 ` Greg Troxel [this message]
2012-08-06 13:17 ` Julien Danjou
2012-08-06 14:30 ` Greg Troxel
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=smu628wdv2o.fsf@linuxpal.mit.edu \
--to=gdt@work.lexort.com \
--cc=ding@gnus.org \
--cc=julien@danjou.info \
/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).