Gnus development mailing list
 help / color / mirror / Atom feed
From: krause@sdbk.de (Sebastian D.B. Krause)
Subject: v5-10 branch created (was: FIXED: Gnus 5.10.6 slow getting new news)
Date: Mon, 29 Mar 2004 01:00:09 +0200	[thread overview]
Message-ID: <87brmgk26e.fsf@news.sdbk.de> (raw)
In-Reply-To: <ilueksj6ng6.fsf@latte.josefsson.org>

Simon Josefsson <jas@extundo.com> wrote:
> krause@sdbk.de (Sebastian D.B. Krause) writes:
>> Kevin Greiner <kgreiner@xpediantsolutions.com> wrote:
>>> The patch has been checked in.
>>
>> Can you please provide a backport of this patch for Gnus 5.10.6?
>
> (Generalizing the issue somewhat:)
>
> Do we want more 5.10 releases?  I think so.  There isn't a v5-10
> branch as far as I can tell, but I guess it could be created based
> on v5-10-6.  Ok to create it, Lars?  Then we could apply the above
> back port.  I think there was one other largish bug in 5.10.6 too,
> but I don't recall exactly when it was discussed.  I guess there
> doesn't have to be a proper 5.10.7 soonish, a CVS branch for 5.10
> should suffice for Debian, the XEmacs package etc.

After another email of today, Lars has just created a v5-10 branch:

http://quimby.gnus.org/cgi-bin/cvsweb.cgi/gnus/?only_with_tag=v5-10

So development of Gnus 5.10 can continue now and a backport of the
patch for No Gnus above would be nice. :)




      parent reply	other threads:[~2004-03-28 23:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-17 19:59 Gnus 5.10.6 slow getting new news kspost
2004-01-19  3:43 ` Kevin Greiner
2004-01-22  4:03   ` FIXED: " Kevin Greiner
2004-01-22  7:10     ` Andreas Jaeger
2004-02-23 19:20     ` Sebastian D.B. Krause
2004-02-25 18:09       ` Simon Josefsson
2004-02-25 19:01         ` Sebastian D.B. Krause
2004-03-28 23:00         ` Sebastian D.B. Krause [this message]

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=87brmgk26e.fsf@news.sdbk.de \
    --to=krause@sdbk.de \
    /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).