From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: Just a bit confused about following gnus devel branch
Date: Mon, 06 Feb 2012 07:34:57 +0100 [thread overview]
Message-ID: <87mx8wtqpa.fsf@dod.no> (raw)
In-Reply-To: <87zkcxpggu.fsf@newsguy.com>
>>>>> 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)
prev parent reply other threads:[~2012-02-06 6:34 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
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 [this message]
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=87mx8wtqpa.fsf@dod.no \
--to=sb@dod.no \
--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).