From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Tracking Current Org Version
Date: Sat, 09 Aug 2014 16:54:17 +0200 [thread overview]
Message-ID: <87zjfdogrq.fsf@Rainer.invalid> (raw)
In-Reply-To: 87tx5n9ejn.fsf@be.cs.appstate.edu
Kenneth Jacker writes:
> For me, there is a little confusion on just which version I'm using ...
>
> I changed to the org-mode "git managed" directory, and entered:
>
> $ make update
>
> { Do I need to do more? I followed the above with
> "make" and "make install" ... necessary? }
Well, if you do that, then "make up2" is what you really want. It does
the above plus it doesn't install if the tests fail, so you aren't hosed
if you happen to build at a time where Org is broken.
> After performing the above yesterday and then checking with "M-x org-version" shows:
>
> Org-mode version 8.3beta (release_8.3beta-175-g59cd25
>
> Is that the latest? No date is included ...
Nor is there any need for that. The version string tells you that the
most recently "tagged" release version is 8.3beta, there have been 175
commits since then and the commit you're on has an SHA1 starting with
59cd25 (i.e. 'git show 59cd25' will let you look at that commit and 'git
log 59cd25' shows the changes from that point backward).
> In addition, I receive announcements from <elpa.gnu.org> that shows things like:
>
> Latest: org-20140804.tar, 2014-Aug-04, 5.21MB
>
> How does *that* differ/compare to what 'git' is downloading?
ELPA is fed by the "maint" branch, not master. In a nutshell, between
releases maint only gets bugfixes, while master can remove, change or
add features at any time. If you are using master, you should be
following the mailing list at least (and know how to install a different
version than the last one for the few times where one of those changes
on master may impact you).
> What is the "best" way to do this? ;-)
Whatever you prefer.
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
prev parent reply other threads:[~2014-08-09 14:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 15:39 Tracking Current Org Version Kenneth Jacker
2014-08-09 6:08 ` Suvayu Ali
2014-08-09 14:25 ` Kenneth Jacker
2014-08-09 15:38 ` Suvayu Ali
2014-08-09 14:54 ` Achim Gratz [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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zjfdogrq.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=emacs-orgmode@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).