From: andrea Crotti <andrea.crotti.0@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Exporting after executing code
Date: Mon, 14 Sep 2009 13:27:13 +0000 (UTC) [thread overview]
Message-ID: <loom.20090914T152502-166@post.gmane.org> (raw)
In-Reply-To: m2skeshvob.fsf@gmail.com
Fantastic, Now I finally found how I will write my servers
documentation, but still I have to decide how to proceed.
I have a git repository in /etc, so every important file is under
revision control.
I have two options I think:
- move everything on the server and link the config files with absolute path
(/etc/conf.conf)
- keep everything local and create a git server which I pull every time I make
a change.
The documentation should stay there always on the server
automatically published in html format, so maybe the first
solution is better. But the second solution is more flexible and
I would have less problems with emacs and remote processes.
What would you suggest?
prev parent reply other threads:[~2009-09-14 13:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 12:41 Exporting after executing code andrea Crotti
2009-09-11 13:48 ` Detlef Steuer
2009-09-11 15:04 ` andrea Crotti
2009-09-11 15:53 ` Nick Dokos
2009-09-11 16:54 ` andrea Crotti
2009-09-11 17:57 ` Sebastian Rose
2009-09-11 20:34 ` Carsten Dominik
2009-09-12 17:38 ` andrea Crotti
2009-09-12 18:20 ` Eric Schulte
2009-09-14 13:27 ` andrea Crotti [this message]
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=loom.20090914T152502-166@post.gmane.org \
--to=andrea.crotti.0@gmail.com \
--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).