From: Julien Danjou <julien@danjou.info>
To: ding@gnus.org
Cc: lukasz.stelmach@iem.pw.edu.pl
Subject: Re: Problem replying to emails today
Date: Wed, 21 Sep 2011 15:35:06 +0200 [thread overview]
Message-ID: <87sjnqnhmd.fsf@keller.adm.naquadah.org> (raw)
In-Reply-To: <87vcsm59ut.fsf@pinto.chemeng.ucl.ac.uk> (Eric S. Fraga's message of "Wed, 21 Sep 2011 14:00:10 +0100")
[-- Attachment #1: Type: text/plain, Size: 975 bytes --]
On Wed, Sep 21 2011, Eric S Fraga wrote:
> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>
>>> From: Lars Magne Ingebrigtsen <larsi@gnus.org>
>>> To: ding@gnus.org
>>
>>> Subject: Re: Problem replying to emails today
>>>
>>> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>>>
>>> > message-checksum: Search failed: "^--text follows this line--$"
>>>
>>> `(setq debug-on-error t)', repeat the bug and post the resulting
>>> backtrace.
>>
>> I did but forgot to say so, sorry. It is not an error so there is no
>> backtrace! Only that message above is generated.
>>
>> I will try git bisect when I get a chance.
>
> commit 1b53ab636f0852054bc27624f086bb524f71667f seems to be the one
> causing the problems, at least for me. reverting just that one commit
> fixes gnus.
>
> I'm slowly getting to grips with git (as a mercurial user)...
Ok, I though it was this commit. I'm adding Łukasz in Cc so he can check
what is happening.
--
Julien Danjou
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2011-09-21 13:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 11:21 Eric S Fraga
2011-09-21 11:27 ` Julien Danjou
2011-09-21 11:32 ` Lars Magne Ingebrigtsen
2011-09-21 12:39 ` Eric S Fraga
2011-09-21 13:00 ` Eric S Fraga
2011-09-21 13:35 ` Julien Danjou [this message]
2011-09-25 10:14 ` Łukasz Stelmach
2011-09-25 16:25 ` Łukasz Stelmach
2011-09-21 14:11 ` Lars Magne Ingebrigtsen
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=87sjnqnhmd.fsf@keller.adm.naquadah.org \
--to=julien@danjou.info \
--cc=ding@gnus.org \
--cc=lukasz.stelmach@iem.pw.edu.pl \
/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).