From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Ma Gnus v0.1 is released
Date: Wed, 01 Feb 2012 13:13:59 -0500 [thread overview]
Message-ID: <87ty3axvyw.fsf@lifelogs.com> (raw)
In-Reply-To: <jpzkd3lrws.fsf@news.eternal-september.org>
On Tue, 31 Jan 2012 17:10:11 +0000 Richard Riley <rileyrg@gmail.com> wrote:
RR> Is Ma Gnus a replacement for nognus for those of us wanting your latest
RR> and greatest alongside, say, emacs 24 where the emacs 24 version of gnus
RR> is frozen?
Ma Gnus is the name of what you get in the master branch of the Gnus Git
repo. No Gnus used to be it, but now No Gnus has been branched off master.
So before you had the commit history (branch names in *markers*):
A->B->C->D->*master* AKA No Gnus
Now you have
A->B->C->D->E->F->*master* AKA Ma Gnus
A->B->C->D->P->Q->F->*no-gnus* AKA No Gnus
Which means that they had a common history up to the branching point
after D, and some commits like F may be shared between the branches.
I strongly recommend the digitally free and excellent "Pro Git" book by
Scott Chacon, if you want to learn Git a little better. It will help
make sense of branching, especially.
Ted
next prev parent reply other threads:[~2012-02-01 18:13 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
2012-02-01 18:13 ` Ted Zlatanov [this message]
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=87ty3axvyw.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).