Gnus development mailing list
 help / color / mirror / Atom feed
From: Miles Bader <miles@gnu.org>
To: ding@gnus.org
Subject: Re: Getting Reacquainted with Gnus
Date: Mon, 04 Aug 2008 16:21:33 +0900	[thread overview]
Message-ID: <buo63qhqm82.fsf@dhapc248.dev.necel.com> (raw)
In-Reply-To: <m2zlny3aoa.fsf@aviatrix.h.ajcos.net>

Andrew J Cosgriff <confusenet@polydistortion.net> writes:
>> I still don't know what version I should be using.  I guess the only
>> thing newer than 5.13 would be a development snapshot?
>
> Yes, though I believe Emacs CVS is synced up with Gnus CVS fairly(?)
> regularly these days.

Yes.  Currently "regularly" is about every 2-3 weeks.

> For the time being it seems like the latest, best Gnus is whatever your
> Emacs ships with.

That's pretty much true if you're using Emacs from the CVS trunk.

> If you want anything more recent, you're best pulling it down via CVS,
> since actual development "releases" are pretty few and far between
> these days, it seems.

More or less, though Gnus development releases might be useful for
people that don't want to run a CVS Emacs, but want a newer Gnus.

BTW, another point that might be worth mentioning is that the Gnus bug
reporting email addresses don't seem to reach anybody, or at least, the
only way I've found to get a response is to send to the development
mailing list.

-Miles

-- 
XML is like violence.  If it doesn't solve your problem, you're not
using enough of it.




  parent reply	other threads:[~2008-08-04  7:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-31  0:42 David Abrahams
2008-07-31  5:06 ` Andrew J Cosgriff
2008-07-31 23:39   ` Ian Swainson
2008-08-04  7:21   ` Miles Bader [this message]
2008-08-09 18:03   ` Adam Sjøgren
2008-08-10  0:43   ` Andrew J Cosgriff
2008-07-31 18:21 ` Ted Zlatanov

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=buo63qhqm82.fsf@dhapc248.dev.necel.com \
    --to=miles@gnu.org \
    --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).