From: Bernt Hansen <bernt@norang.ca>
To: Daniel Brunner <daniel@dbrunner.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: [org-babel] Does org-babel needs some simplification?
Date: Wed, 30 Jun 2010 20:37:33 -0400 [thread overview]
Message-ID: <8739w49gvm.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <871vbos4hu.fsf@systemhaus-brunner.de> (Daniel Brunner's message of "Wed\, 30 Jun 2010 21\:30\:05 +0200")
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
next prev parent reply other threads:[~2010-07-01 0:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 3:51 [org-babel] Does org-babel needs some simplification? Torsten Wagner
2010-06-29 4:28 ` Erik Iverson
2010-06-29 18:07 ` Eric Schulte
2010-06-29 4:36 ` Carsten Dominik
2010-06-29 7:29 ` Thomas S. Dye
2010-06-29 18:01 ` Eric Schulte
2010-06-30 19:30 ` Daniel Brunner
2010-06-30 21:56 ` Jonathan Arkell
2010-07-01 0:37 ` Bernt Hansen [this message]
2010-07-01 2:36 ` Torsten Wagner
2010-07-01 20:53 ` Eric Schulte
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=8739w49gvm.fsf@gollum.intra.norang.ca \
--to=bernt@norang.ca \
--cc=daniel@dbrunner.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).