From: Bernt Hansen <bernt@norang.ca>
To: "Jörg Hagmann" <joerg.hagmann@unibas.ch>
Cc: Emacs-orgmode@gnu.org
Subject: Re: agenda-ignore-date and version number
Date: Thu, 29 Jul 2010 07:37:56 -0400 [thread overview]
Message-ID: <87sk32ikmj.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <4C513288.7040808@unibas.ch> ("Jörg Hagmann"'s message of "Thu, 29 Jul 2010 09:49:28 +0200")
Jörg Hagmann <joerg.hagmann@unibas.ch> writes:
> 2. Since 7.01, M-x org-version always reports "Org-mode version
> 7.01trans" after a "git pull | make clean | make | make install | make
> install-info" sequence. How can I be sure that my installation really
> gets updated? And why do others report detailed version numbers (after
> "trans"), not just "trans"? Do they use a different command?
It is the same M-x org-version command. If you are running org-mode
from a git repository and git is available in your path then the M-x
org-version command will report the current commit you are at as part of
the version information.
Org-mode version 7.01trans (release_7.01g.37.g3ee6)
The 7.01trans is the version number in the emacs lisp source files. The
'trans' part indicates it is the development branch sometime after the
latest 7.01 release. The git describe output (release_7.01g.37.g3ee6)
just gives precise details of exactly where you are in the repository.
The reported git release version is always the commit you have currently
checked out. If you are running older compiled sources then it will
report incorrect information -- you're really running the older compiled
version even though your current checkout is something else. You can
reload your version with M-x org-reload and C-u M-x org-reload (to run
from source files, not compiled versions if they exist)
HTH,
Bernt
next prev parent reply other threads:[~2010-07-29 11:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 7:49 agenda-ignore-date and version number Jörg Hagmann
2010-07-29 11:37 ` Bernt Hansen [this message]
2010-08-01 18:43 ` David Maus
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=87sk32ikmj.fsf@gollum.intra.norang.ca \
--to=bernt@norang.ca \
--cc=Emacs-orgmode@gnu.org \
--cc=joerg.hagmann@unibas.ch \
/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).