Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Stern <dodecatheon@gmail.com>
To: ding@gnus.org
Subject: when will it be safe to leave the bunker?
Date: Mon, 13 Dec 2010 10:50:04 -0800	[thread overview]
Message-ID: <lspvd2xcxsz.fsf@saturna.ca.boeing.com> (raw)

I am a longtime user of Gnus and Emacs from anoncvs.

I stopped updating my version a couple of months back when Lars ramped
up his coding activity.

In the past, he has done his Gnus work in intense sessions between
other activities, and after a couple of weeks the dust clears and it
is safe to update again.

This time Lars has been quite involved for a couple of months and
shows no sign of flagging energy.

I will have to cope with switching to bazaar and git for this update,
so I don't want to get started until activity on the tree has settled
down a bit.

So Lars, I'm just wondering:  when will it be safe for this ostrich to
pull his head out of the sand?  :-)

Thanks,

Ted
-- 
 Frango ut patefaciam -- I break so that I may reveal



             reply	other threads:[~2010-12-13 18:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-13 18:50 Ted Stern [this message]
2010-12-13 19:12 ` 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=lspvd2xcxsz.fsf@saturna.ca.boeing.com \
    --to=dodecatheon@gmail.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).