From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Just a bit confused about following gnus devel branch
Date: Sun, 05 Feb 2012 09:23:04 -0500 [thread overview]
Message-ID: <87obtd8ilz.fsf@lifelogs.com> (raw)
In-Reply-To: <87zkcxpggu.fsf@newsguy.com>
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
next prev parent reply other threads:[~2012-02-05 14:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-05 13:17 Harry Putnam
2012-02-05 14:23 ` Ted Zlatanov [this message]
2012-02-05 14:40 ` Harry Putnam
2012-02-05 16:26 ` Tassilo Horn
2012-02-09 14:01 ` Harry Putnam
2012-02-09 14:09 ` Tassilo Horn
2012-02-05 15:28 ` Richard Riley
2012-02-06 3:57 ` Dave Goldberg
2012-02-05 20:27 ` Antoine Levitt
2012-02-06 1:34 ` Katsumi Yamaoka
2012-02-06 6:34 ` 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=87obtd8ilz.fsf@lifelogs.com \
--to=tzz@lifelogs.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).