From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: Re: Bug in current v14 - no followup or reply possible
Date: Wed, 23 Feb 2011 10:50:30 -0600 [thread overview]
Message-ID: <87hbbuu23t.fsf@newsguy.com> (raw)
In-Reply-To: <m2fwrerbf3.fsf@ecocode.net>
Erik Colson <eco@ecocode.net> writes:
> Harry Putnam <reader@newsguy.com> writes:
>
>> Erik Colson <eco@ecocode.net> writes:
>>
>>> Harry Putnam <reader@newsguy.com> writes:
>>>
>>>> I guess no one else besides Steiner and me are noticing this problem,
>>>> but for me it is thoroughly reproducable so much so that I have to
>>>> fall back to my older v11 to be able to post at all.
>>>
>>> Well no, I had the problem too. But the patch sent to the list solved
>>> the problem...
>>
>> Looking for messages from `colson' in the last 300 posts, I don't see
>> your patch.
>>
>>
>
> Of course not. The patch was not mine ;)
Good reason hehe... but your message made it sound like it was yours.
Sorry for my misread.
> Here is the mail from David with the patch included.
> But, I think it has been applied to the git repo, so you might just
> check out the latest version from it...
Yes its all working now, but one further comment about that patch:
Of course I saw I that patch, but I'll tell you, it was not made clear
in any way what the heck it was supposed to do in subject or message
body, unless you happened to notice the term `winconf-name' in subject
and already new that term showed up in back-traces of the problem.
Further, the patch failed for Ted Z. So it was not clear at all what
it was for or even if it worked.
next prev parent reply other threads:[~2011-02-23 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 6:23 Harry Putnam
2011-02-23 6:49 ` Erik Colson
2011-02-23 15:50 ` Harry Putnam
2011-02-23 15:57 ` Erik Colson
2011-02-23 16:50 ` Harry Putnam [this message]
2011-02-23 8:05 ` Lars Ingebrigtsen
2011-02-23 16:05 ` Harry Putnam
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=87hbbuu23t.fsf@newsguy.com \
--to=reader@newsguy.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).