From: Erik Colson <eco@ecocode.net>
To: Harry Putnam <reader@newsguy.com>
Cc: ding@gnus.org
Subject: Re: Bug in current v14 - no followup or reply possible
Date: Wed, 23 Feb 2011 07:49:00 +0100 [thread overview]
Message-ID: <m2ei6zutyb.fsf@ecocode.net> (raw)
In-Reply-To: <87ei6zs1zv.fsf@newsguy.com> (Harry Putnam's message of "Wed, 23 Feb 2011 00:23:32 -0600")
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...
Best
--
erik colson
ecocode.net
next prev parent reply other threads:[~2011-02-23 6:49 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 [this message]
2011-02-23 15:50 ` Harry Putnam
2011-02-23 15:57 ` Erik Colson
2011-02-23 16:50 ` Harry Putnam
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=m2ei6zutyb.fsf@ecocode.net \
--to=eco@ecocode.net \
--cc=ding@gnus.org \
--cc=reader@newsguy.com \
/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).