From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: Re: No Gnus v0.13 is released
Date: Mon, 21 Feb 2011 20:53:31 -0600 [thread overview]
Message-ID: <87mxlopyok.fsf@newsguy.com> (raw)
In-Reply-To: <87fwrgssh1.fsf@gnus.org>
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Harry Putnam <reader@newsguy.com> writes:
>
>> That doesn't appear to work here, maybe I've done something wrong?
>
> [...]
>
>> | HEAD is now at f68a008... No Gnus v0.13 is released
>
> I think this means that it worked.
Egad... after all this time the `No' can still throw my pea brain
next prev parent reply other threads:[~2011-02-22 2:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 0:23 Lars Ingebrigtsen
2011-02-22 0:33 ` Lars Ingebrigtsen
2011-02-22 17:41 ` Ted Zlatanov
2011-02-22 2:31 ` Harry Putnam
2011-02-22 2:39 ` Lars Ingebrigtsen
2011-02-22 2:53 ` Harry Putnam [this message]
2011-02-22 3:25 ` Raphael Kubo da Costa
2011-02-22 17:09 ` Jeremy Hankins
2011-02-22 21:25 ` Steinar Bang
2011-02-22 22:37 ` Jeremy Hankins
2011-02-23 6:39 ` Steinar Bang
2011-02-23 8:19 ` Lars 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=87mxlopyok.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).