Just a bit confused about following gnus devel branch

Just a bit confused about following gnus devel branch

[Harry Putnam]

I've followed some of the discussion of gnus development plans,
nognus, magnus, but didn't really understand what is happening there. 

I'm left not having a clue of how a gnus users who has tracked
nognus from way back through its other names is to continue tracking
the development branch.

Can someone say definitively, what git command is required now to
start and continue tracking the development branch of gnus?
 

Re: Just a bit confused about following gnus devel branch

[Ted Zlatanov]

On Sun, 05 Feb 2012 08:17:21 -0500 Harry Putnam <reader@newsguy.com> wrote: 

HP> I've followed some of the discussion of gnus development plans,
HP> nognus, magnus, but didn't really understand what is happening there. 

HP> I'm left not having a clue of how a gnus users who has tracked
HP> nognus from way back through its other names is to continue tracking
HP> the development branch.

HP> Can someone say definitively, what git command is required now to
HP> start and continue tracking the development branch of gnus?

We're doing a basic "branch per release" approach as explained in
http://www.codinghorror.com/blog/2007/10/software-branching-and-parallel-universes.html

The "master" branch is development.  Currently that's known as Ma (真)
Gnus.  No Gnus lives in a new branch called "no-gnus" which was branched
off 5 days ago; until then No Gnus was "master".  We're simply branching
off older versions for bug fixes and maintenance, while we're keeping
the "master" branch as the development branch as it's always been.

So, you just need to clone the gnus.git repo.  You should be in the
"master" branch by default (type "git branch" to be sure).  If you're
not, "git checkout master" will do it.

Ted

Re: Just a bit confused about following gnus devel branch

[Harry Putnam]

Ted Zlatanov <tzz@lifelogs.com> writes:

> On Sun, 05 Feb 2012 08:17:21 -0500 Harry Putnam <reader@newsguy.com> wrote: 
>
> HP> I've followed some of the discussion of gnus development plans,
> HP> nognus, magnus, but didn't really understand what is happening there. 
>
> HP> I'm left not having a clue of how a gnus users who has tracked
> HP> nognus from way back through its other names is to continue tracking
> HP> the development branch.
>
> HP> Can someone say definitively, what git command is required now to
> HP> start and continue tracking the development branch of gnus?
>
> We're doing a basic "branch per release" approach as explained in
> http://www.codinghorror.com/blog/2007/10/software-branching-and-parallel-universes.html
>
> The "master" branch is development.  Currently that's known as Ma (真)
> Gnus.  No Gnus lives in a new branch called "no-gnus" which was branched
> off 5 days ago; until then No Gnus was "master".  We're simply branching
> off older versions for bug fixes and maintenance, while we're keeping
> the "master" branch as the development branch as it's always been.
>
> So, you just need to clone the gnus.git repo.  You should be in the
> "master" branch by default (type "git branch" to be sure).  If you're
> not, "git checkout master" will do it.

And the gnus.git repo is currently where?

Re: Just a bit confused about following gnus devel branch

[Tassilo Horn]

Harry Putnam <reader@newsguy.com> writes:

Hi Harry,

> And the gnus.git repo is currently where?

Where it has been the last few years:

  https://git.gnus.org/gnus.git

Bye,
Tassilo

Re: Just a bit confused about following gnus devel branch

[Harry Putnam]

Tassilo Horn <tassilo@member.fsf.org> writes:

> Harry Putnam <reader@newsguy.com> writes:
>
> Hi Harry,
>
>> And the gnus.git repo is currently where?
>
> Where it has been the last few years:
>
>   https://git.gnus.org/gnus.git

Ackk and so it is.  Sorry for my confusion.

Re: Just a bit confused about following gnus devel branch

[Tassilo Horn]

Harry Putnam <reader@newsguy.com> writes:

>>> And the gnus.git repo is currently where?
>>
>> Where it has been the last few years:
>>
>>   https://git.gnus.org/gnus.git
>
> Ackk and so it is.  Sorry for my confusion.

No problem, we already got used to it. ;-)

SCNR,
Tassilo

Re: Just a bit confused about following gnus devel branch

[Richard Riley]

Ted Zlatanov <tzz@lifelogs.com> writes:

> On Sun, 05 Feb 2012 08:17:21 -0500 Harry Putnam <reader@newsguy.com> wrote: 
>
> HP> I've followed some of the discussion of gnus development plans,
> HP> nognus, magnus, but didn't really understand what is happening there. 
>
> HP> I'm left not having a clue of how a gnus users who has tracked
> HP> nognus from way back through its other names is to continue tracking
> HP> the development branch.
>
> HP> Can someone say definitively, what git command is required now to
> HP> start and continue tracking the development branch of gnus?
>
> We're doing a basic "branch per release" approach as explained in
> http://www.codinghorror.com/blog/2007/10/software-branching-and-parallel-universes.html
>
> The "master" branch is development.  Currently that's known as Ma (真)

Is "ma" for master? Naming horrors ;) Daily people ask what "no gnus"
means in #emacs and similar. I guess its to continue. I too was
completely bedazzled by the new changes merely on the basis of the
names.

Re: Just a bit confused about following gnus devel branch

[Dave Goldberg]

> Is "ma" for master? Naming horrors ;) Daily people ask what "no gnus"
> means in #emacs and similar. I guess its to continue. I too was
> completely bedazzled by the new changes merely on the basis of the
> names.

The answer is in the Gnus info file.  Check the History/Gnus Versions section under the Appendices.

-- 
Dave Goldberg
david.goldberg6@verizon.net

Re: Just a bit confused about following gnus devel branch

[Antoine Levitt]

05/02/12 15:23, Ted Zlatanov
> On Sun, 05 Feb 2012 08:17:21 -0500 Harry Putnam <reader@newsguy.com> wrote: 
>
> HP> I've followed some of the discussion of gnus development plans,
> HP> nognus, magnus, but didn't really understand what is happening there. 
>
> HP> I'm left not having a clue of how a gnus users who has tracked
> HP> nognus from way back through its other names is to continue tracking
> HP> the development branch.
>
> HP> Can someone say definitively, what git command is required now to
> HP> start and continue tracking the development branch of gnus?
>
> We're doing a basic "branch per release" approach as explained in
> http://www.codinghorror.com/blog/2007/10/software-branching-and-parallel-universes.html
>
> The "master" branch is development.  Currently that's known as Ma (真)
> Gnus.  No Gnus lives in a new branch called "no-gnus" which was branched
> off 5 days ago; until then No Gnus was "master".  We're simply branching
> off older versions for bug fixes and maintenance, while we're keeping
> the "master" branch as the development branch as it's always been.
>
> So, you just need to clone the gnus.git repo.  You should be in the
> "master" branch by default (type "git branch" to be sure).  If you're
> not, "git checkout master" will do it.

What about synchronisation with emacs? Does emacs track nognus? Will it
continue doing so after feature freeze? Do I have to track gnus
specifically in addition to emacs to benefit from the latest features?

Re: Just a bit confused about following gnus devel branch

[Katsumi Yamaoka]

antoine.levitt@gmail.com wrote:

AFAIU, and what I'm doing is:

> What about synchronisation with emacs?
> Does emacs track nognus?

Emacs trunk and Gnus no-gnus branch are being synchronized now.

> Will it continue doing so after feature freeze?

I'm going to make Emacs trunk and Gnus trunk (Ma gnus) get synch'd
after Emacs 24.1 release.

> Do I have to track gnus specifically in addition to emacs to benefit
> from the latest features?

Re: Just a bit confused about following gnus devel branch

[Steinar Bang]

>>>>> Harry Putnam <reader@newsguy.com>:

> Can someone say definitively, what git command is required now to
> start and continue tracking the development branch of gnus?
 
 mkdir ~/git/
 git clone http://git.gnus.org/gnus.git
 cd gnus
 ./configure
 make; cd lisp; make tags

If you do "git branch" in the ~/git/gnus/ directory, you will see that
you are on the master branch.  This is where gnus development will take
place. 

To update, I do these two commands:
 (cd ~/git/gnus; git pull)
 (cd ~/git/gnus; make clean; make; cd lisp; make tags)