From: Yagnesh Raghava Yakkala <yagnesh@live.com>
To: ding@gnus.org
Subject: Re: Ma Gnus v0.1 is released
Date: Wed, 01 Feb 2012 15:26:32 +0900 [thread overview]
Message-ID: <87y5snjch3.fsf@live.com> (raw)
In-Reply-To: <7hobtjkv6e.fsf@news.eternal-september.org>
Richard Riley <rileyrg@gmail.com> writes:
> Yagnesh Raghava Yakkala <yagnesh@live.com> writes:
>
>> Richard Riley <rileyrg@gmail.com> writes:
>>
>>> Lars Ingebrigtsen <larsi@gnus.org> 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
next prev parent reply other threads:[~2012-02-01 6:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 16:59 Lars Ingebrigtsen
2012-01-31 17:10 ` Richard Riley
2012-02-01 1:17 ` Yagnesh Raghava Yakkala
2012-02-01 4:57 ` Richard Riley
2012-02-01 6:26 ` Yagnesh Raghava Yakkala [this message]
2012-02-01 18:13 ` Ted Zlatanov
2012-02-01 22:02 ` Steinar Bang
2012-01-31 17:38 ` Frank Haun
2012-02-01 13:04 ` Harry Putnam
2012-02-01 13:36 ` Steinar Bang
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=87y5snjch3.fsf@live.com \
--to=yagnesh@live.com \
--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).