From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/68796 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel,gmane.emacs.gnus.general Subject: Re: Gnus branches and sync with Emacs Date: Tue, 21 Jul 2009 15:07:48 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <87zlaxol4b.fsf@lifelogs.com> References: <87eisdn3ng.fsf@marauder.physik.uni-ulm.de> <87skgri803.fsf@lifelogs.com> <871vobdxpu.fsf@stupidchicken.com> <87eisbw0gf.fsf@marauder.physik.uni-ulm.de> <87zlayf26p.fsf@lifelogs.com> <87tz16t09n.fsf@marauder.physik.uni-ulm.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1248206902 22721 80.91.229.12 (21 Jul 2009 20:08:22 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 21 Jul 2009 20:08:22 +0000 (UTC) Cc: ding@gnus.org To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jul 21 22:08:14 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MTLdF-0004Fw-Fw for ged-emacs-devel@m.gmane.org; Tue, 21 Jul 2009 22:08:14 +0200 Original-Received: from localhost ([127.0.0.1]:50417 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MTLdE-0005Gg-TO for ged-emacs-devel@m.gmane.org; Tue, 21 Jul 2009 16:08:12 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MTLdB-0005G6-2Z for emacs-devel@gnu.org; Tue, 21 Jul 2009 16:08:09 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MTLd6-0005Ev-H4 for emacs-devel@gnu.org; Tue, 21 Jul 2009 16:08:08 -0400 Original-Received: from [199.232.76.173] (port=38567 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MTLd6-0005Es-EJ for emacs-devel@gnu.org; Tue, 21 Jul 2009 16:08:04 -0400 Original-Received: from main.gmane.org ([80.91.229.2]:40696 helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MTLd5-0006pq-L3 for emacs-devel@gnu.org; Tue, 21 Jul 2009 16:08:04 -0400 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1MTLd2-0001wj-3V for emacs-devel@gnu.org; Tue, 21 Jul 2009 20:08:00 +0000 Original-Received: from 38.98.147.130 ([38.98.147.130]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 21 Jul 2009 20:08:00 +0000 Original-Received: from tzz by 38.98.147.130 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 21 Jul 2009 20:08:00 +0000 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 35 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 38.98.147.130 X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.1.50 (gnu/linux) Cancel-Lock: sha1:nsJd5IA2wny9IdL6sX2ohgp8bEE= X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:112950 gmane.emacs.gnus.general:68796 Archived-At: On Tue, 21 Jul 2009 19:27:00 +0200 Reiner Steib wrote: >> Then the burden falls on Reiner or others to backport things into >> the "for Emacs" branch when appropriate. RS> The "burden" basically is on Miles, but it's more or less RS> automatically. Well, at least if every developer commits bugfixes to RS> the bugfix-branch (which will be synced to the development branch) by RS> Miles. Actually the burden is now on the Gnus developers to backport their changes to the bugfix Gnus branch in your scenario. The actual followup sync is up to Miles. With CVS this is a bit of a pain (compared to SVN, Git, etc.) so I hope we can move Gnus development off CVS soon. Not that I am complaining about backporting, it's not a lot of work, it's just tedious. >> This would bring the Gnus CVS trunk back to the "bleeding edge" status >> it had in the past. RS> The Gnus trunk also had long stabilizing periods (e.g. from 5.10.1 to RS> 5.10.6). Sure. The online info, however, says: http://www.gnus.org/distribution.html "Please note that what you're getting is probably not even a bleeding-edge Gnus, but a severly hemorrhaging one." so I think stability is supposed to be an exception, at least when that was written. We should probably revise gnus.org anyhow, lots of the information is outdated. Ted