From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bernt Hansen <bernt@norang.ca>
Subject: Re: [org-babel] Does org-babel needs some simplification?
Date: Wed, 30 Jun 2010 20:37:33 -0400
Message-ID: <8739w49gvm.fsf@gollum.intra.norang.ca>
References: <4C296DDA.1080109@gmail.com> <871vbos4hu.fsf@systemhaus-brunner.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from [140.186.70.92] (port=50397 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OU7mu-0003Af-O2
	for emacs-orgmode@gnu.org; Wed, 30 Jun 2010 20:37:58 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <bernt@norang.ca>) id 1OU7ms-0006po-Hw
	for emacs-orgmode@gnu.org; Wed, 30 Jun 2010 20:37:56 -0400
Received: from mho-01-ewr.mailhop.org ([204.13.248.71]:51777)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <bernt@norang.ca>) id 1OU7ms-0006pH-GO
	for emacs-orgmode@gnu.org; Wed, 30 Jun 2010 20:37:54 -0400
In-Reply-To: <871vbos4hu.fsf@systemhaus-brunner.de> (Daniel Brunner's message
	of "Wed\, 30 Jun 2010 21\:30\:05 +0200")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Daniel Brunner <daniel@dbrunner.de>
Cc: emacs-orgmode@gnu.org

Daniel Brunner <daniel@dbrunner.de> writes:

> I know, org-mode is a growing project and I really really like the
> org-babel features. But for me it is now not advisable any more to keep
> on the master branch. Today I spent several hours for finding the
> reasons why something is not working any more. And that is too much for
> a productive environment. 

I too run my production org-mode stuff from the master branch.  If you
pull and things break you can just step back to the commit you were at
before your pull with

$ git checkout ORIG_HEAD

All of your local commit changes should be available in the reflog so
you can go back to any recent point in time in your repository.

$ git reflog

will show a list of commits you have visited recently and you can return
to any one with a checkout of the SHA1 or by using the HEAD@{n} shortcut
-- just beware that HEAD@{n} changes everytime you move HEAD on your
repository.

Another method is to tag commits you know are good - so you can return
to them easily using whatever-name-you-like.

HTH,
Bernt