Gnus development mailing list
 help / color / mirror / Atom feed
From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: Proposed Changes
Date: Tue, 13 Apr 2004 22:55:53 -0500	[thread overview]
Message-ID: <uisg3usae.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <v965c3u5ol.fsf@marauder.physik.uni-ulm.de>

Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:

> On Tue, Apr 13 2004, Kevin Greiner wrote:
>
>> krause@sdbk.de (Sebastian D.B. Krause) writes:
>>> Larsi has created the v5-10 branch in the Gnus CVS for that but I
>>> still don't see any backports of bugfixes (especially
>>> <uektshbot.fsf_-_@xpediantsolutions.com>) or other checkins into
>>> this branch. This branch could also be used to provide a base for
>>> fixes that e.g. could go into the Debian package of Gnus.
>>
>> I'd like to get a clarification on how the v5-10 branch is to be
>> handled.  
>
> I think you can simply do a checkout of this branch and commit the
> bugfixes (possibly backported from the trunk) there:
>
>   mkdir 5-10
>   cd 5-10
>   cvs -d :pserver:YOURLOGIN@cvs.gnus.org:/usr/local/cvsroot co -r v5-10 gnus 
>
> [ I'm not aware of a more simple possibility, but I'm not too familiar
> with cvs branches. ]

Right choice.  I had forgotten that Lars had already set up the branch
point.

I've updated gnus-agent.el and gnus-cus.el to resolve the agent
performance issues in v5-10.  If I get some positive feedback, I'll
know that it is safe to try to backport the imap integration patches
(So that the agent and cache handle article movement, group renaming,
and group deletion correctly).

Kevin




  reply	other threads:[~2004-04-14  3:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-09  8:53 Gnus 5.10 and Emacs' CVS Frank Schmitt
2004-04-09 10:45 ` Sebastian D.B. Krause
2004-04-10 15:51   ` Kevin Greiner
2004-04-13 11:15   ` Proposed Changes Kevin Greiner
2004-04-13 17:51     ` Reiner Steib
2004-04-14  3:55       ` Kevin Greiner [this message]
2004-04-14  6:38         ` Kai Grossjohann
2004-04-14 16:38           ` Kevin Greiner
2004-04-14 20:00             ` Kai Grossjohann
2004-05-16 13:07             ` Lars Magne Ingebrigtsen
2004-05-16 13:53               ` Kai Grossjohann
2004-05-22 17:20                 ` Lars Magne Ingebrigtsen
2004-04-09 12:48 ` Gnus 5.10 and Emacs' CVS Jesper Harder
2004-04-09 13:03   ` Henrik Enberg
2004-04-09 13:10     ` Jesper Harder
2004-04-09 15:47       ` Frank Schmitt
2004-04-09 16:13         ` Jesper Harder
2004-04-09 18:58           ` Peter Lee
2004-04-09 20:09             ` Romain Francoise
2004-04-09 20:34               ` Sebastian D.B. Krause
2004-04-09 21:58             ` Jesper Harder
2004-04-10  2:10               ` Miles Bader
2004-04-09 16:35         ` Henrik Enberg
2004-04-09 16:37       ` Henrik Enberg

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=uisg3usae.fsf@xpediantsolutions.com \
    --to=kgreiner@xpediantsolutions.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).