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 10:30:49 -0400 [thread overview]
Message-ID: <smuipcwgkiu.fsf@linuxpal.mit.edu> (raw)
In-Reply-To: <87ehnkyxap.fsf@dex.adm.naquadah.org> (Julien Danjou's message of "Mon, 06 Aug 2012 15:17:34 +0200")
[-- Attachment #1: Type: text/plain, Size: 551 bytes --]
Julien Danjou <julien@danjou.info> writes:
> I know, but what you pointed was not a direct revert, see the changelog.
> I would use git revert directly, but it seems that it's prefered to
> document revert in changelog (correct me if I'm wrong).
Perhaps, but my take is that when the revert is close in time, then it's
just as well to revert the changelog entry, since then the new state is
exactly as if it never happened, which won't confuse anyway. I suppose
there's git revert followed by git commit --amend to destage the
changelog hunk :-)
[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]
prev parent reply other threads:[~2012-08-06 14:30 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
2012-08-06 13:17 ` Julien Danjou
2012-08-06 14:30 ` Greg Troxel [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=smuipcwgkiu.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).