From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: git useage question
Date: Sun, 05 Jun 2011 18:40:26 +0200 [thread overview]
Message-ID: <87mxhw5j0l.fsf@Rainer.invalid> (raw)
In-Reply-To: alpine.BSF.2.00.1106041801230.9739@freire1.furyyjbeyq.arg
Jude DaShiell <jdashiel@shellworld.net> writes:
> I wouldn't be writing this if the documentation were reasonable. Once
> org-mode gets cloned, how is git properly used to update the cloned
> instance on a machine?
If you set up the clone correctly (assuming you use a local branch for
keeping your customizations to the Makefile), all you need to do is
$ git pull && make clean && make install
But there's literally hundreds of different ways to configure things
depending on what you want to do. Please check the orgmode FAQ if one
of the "recipes" for using Git+Orgmode there does what you want,
otherwise you will have to learn about Git first (or in parallel). If
you want to experiment with Git, you can always do another clone locally
so you have something to play with that can be thrown away if you mess
it up.
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
next prev parent reply other threads:[~2011-06-05 16:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-04 22:05 git useage question Jude DaShiell
2011-06-04 22:11 ` Nick Dokos
2011-06-04 22:32 ` Jude DaShiell
2011-06-04 23:17 ` Pieter Praet
2011-06-04 23:26 ` Jude DaShiell
2011-06-05 0:06 ` Pieter Praet
2011-06-05 1:21 ` Nick Dokos
2011-06-05 2:45 ` Jude DaShiell
2011-06-05 16:40 ` Achim Gratz [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-05 10:50 Rustom Mody
2011-06-05 13:27 ` Jude DaShiell
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=87mxhw5j0l.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).