From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/81092 Path: news.gmane.org!not-for-mail From: Yagnesh Raghava Yakkala Newsgroups: gmane.emacs.gnus.general Subject: Re: Ma Gnus v0.1 is released Date: Wed, 01 Feb 2012 15:26:32 +0900 Message-ID: <87y5snjch3.fsf@live.com> References: <87ty3bbyh5.fsf@gnus.org> <87wr8773om.fsf@live.com> <7hobtjkv6e.fsf@news.eternal-september.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1328077695 27308 80.91.229.3 (1 Feb 2012 06:28:15 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 1 Feb 2012 06:28:15 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M29373@lists.math.uh.edu Wed Feb 01 07:28:14 2012 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1RsTfx-0002lD-1y for ding-account@gmane.org; Wed, 01 Feb 2012 07:28:13 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1RsTf3-0001az-H4; Wed, 01 Feb 2012 00:27:17 -0600 Original-Received: from mx2.math.uh.edu ([129.7.128.33]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1RsTez-0001ak-RU for ding@lists.math.uh.edu; Wed, 01 Feb 2012 00:27:13 -0600 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx2.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1RsTev-0003QC-2K for ding@lists.math.uh.edu; Wed, 01 Feb 2012 00:27:13 -0600 Original-Received: from plane.gmane.org ([80.91.229.3]) by quimby.gnus.org with esmtp (Exim 4.72) (envelope-from ) id 1RsTet-0004Gr-1i for ding@gnus.org; Wed, 01 Feb 2012 07:27:07 +0100 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1RsTeq-0002Jk-Vc for ding@gnus.org; Wed, 01 Feb 2012 07:27:04 +0100 Original-Received: from okhotsk19.lowtem.hokudai.ac.jp ([133.87.217.175]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 01 Feb 2012 07:27:04 +0100 Original-Received: from yagnesh by okhotsk19.lowtem.hokudai.ac.jp with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 01 Feb 2012 07:27:04 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 60 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: okhotsk19.lowtem.hokudai.ac.jp User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.93 (gnu/linux) Cancel-Lock: sha1:z2hit3s7RxaJ++vG1Jx9BJJtOzc= X-Spam-Score: -1.9 (-) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:81092 Archived-At: Richard Riley writes: > Yagnesh Raghava Yakkala writes: > >> Richard Riley writes: >> >>> Lars Ingebrigtsen writes: >>> >>>> The initial Ma Gnus release. Nothing changed since No Gnus, other than >>>> the name. >>> >>> Having always struggled to understand what "nognus" meant, I'm equally >>> confused as to what "Ma Gnus" is ;) >>> >>> Is Ma Gnus a replacement for nognus for those of us wanting your latest >>> and greatest alongside, say, emacs 24 where the emacs 24 version of gnus >>> is frozen? >> >> Richard, >> >> IIUC Every new name (no gnus, Ma gnus ....) is kind of new Major version >> of gnus. >> >> So if you want a >> bleeding edge stick to the master. >> stable version stick to the newest name (right now it is Magnus) >> >> Please correct me if I am wrong >> >> Yagnesh >> > > Thanks, I think I follow. But the thread on branching and versioning > hasnt really helped much - seems very confusing and I use git > daily. This new naming is a new thing I guess since nognus has been > around for as long as Ive been a gnus user. I posted up a follow up Q > about what MaGnus is compared to master but there hasnt been a reply as > of yet - apparently bug fixes go there but master is development. (This is my just my understanding sofar. I may well off by 200%) It seems naming for gnus release has long history (gnus info manual has History node). In git sense you can think them as maint branches. Any critical fixes on master(development branch) will be cherry picked to those maint branches. > > Since I use el-get to sync packages including nognus I'm wondering what > exactly I should be cloning now in order to keep "up to date". Is nognus > history? Should I be cloning master or magnus or nognus? > Since el-get recipe file 'nognus.rcp' is just pointing to the master(Its a mistake I think) you don't need to care about all these namings at all. Just `el-get-update' nognus will keep you "up to date" -- YYR