From: Bernt Hansen <bernt@norang.ca>
To: Mikael Fornius <mfo@abc.se>, Steinar Bang <sb@dod.no>
Cc: emacs-orgmode@gnu.org
Subject: Re: How to get the last version of org-mode supporting emacs21?
Date: Wed, 02 Jun 2010 10:18:12 -0400 [thread overview]
Message-ID: <874ohla57f.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: 87hbllq101.fsf@eee.lan
Mikael Fornius <mfo@abc.se> writes:
> I found it in the git log, it says says:
>
> --8<---------------cut here---------------start------------->8---
> commit 31858e5c39404cf2bc745fe05f59c7ce6816db74
> Author: Carsten Dominik <carsten.dominik@gmail.com>
> Date: Tue Apr 21 14:00:24 2009 +0200
>
> End of Emacs 21 support.
>
> commit e0cd12716ac8202d4b5c764dfb57d5d7725be73a
> Author: Carsten Dominik <carsten.dominik@gmail.com>
> Date: Tue Apr 21 10:21:36 2009 +0200
>
> Release 6.26b
> --8<---------------cut here---------------end--------------->8---
>
> So I think using release 6.26b would be recommended. I think you should
> clone the git repo and use the command
>
> git reset --hard e0cd12716ac8202d4b5c764dfb57d5d7725be73a
>
> before make.
Don't do that. That will move your current branch tip to that commit
and throw away all of your current changes (if any) in the working
directory.
If you just want to visit and use the old version do
git checkout release_6.26b
instead.
The tag 'release_6.26b' is commit e0cd12716ac8202d4b5c764dfb57d5d7725be73a.
If you want to make changes on top of release_6.26b then create a new
branch instead with
git checkout -b emacs21 release_6.26b
(naming the branch whatever you like instead of emacs21)
HTH,
Bernt
next prev parent reply other threads:[~2010-06-02 14:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 11:21 How to get the last version of org-mode supporting emacs21? Steinar Bang
2010-06-02 8:42 ` Mikael Fornius
2010-06-02 14:18 ` Bernt Hansen [this message]
2010-06-02 14:45 ` Mikael Fornius
2010-06-02 19:13 ` Steinar Bang
2010-06-02 15:00 ` Dan Davison
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=874ohla57f.fsf@gollum.intra.norang.ca \
--to=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=mfo@abc.se \
--cc=sb@dod.no \
/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).