emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Paul Mead <paul.d.mead@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Using Git to update more than one machine (one without	network access)
Date: Wed, 25 Feb 2009 17:12:12 +0000 (UTC)	[thread overview]
Message-ID: <loom.20090225T170341-347@post.gmane.org> (raw)
In-Reply-To: alpine.DEB.2.00.0902251055010.14503@thedarktrumpet.com

David Thole <dthole <at> gmail.com> writes:

> 
> Paul,
> 
> The way I've accomplished the task you're talking about is instead of 
> trying to push and pull *to* the work machine, I use another machine with 
> less restrictive firewalls to push and pull from.  This is how I do it...
> 
> Work <-> Web Server <-> Home
> 
> The web server acts as my "USB Key", and I have cron jobs to pull and push 
> updates to and from the servers.  So at 7:30, I can have a "git pull" on 
> my work machine - so it would go to the web server, pull in and merge my 
> changes before I got to work.  Then when I go home, say at 5:10, do a "git 
> push" back to the web server.  At 5:30 or so my home machine can do a "git 
> pull" and at 7:00 AM do a "git push".
> 
> This works pretty well so far.  Another solution is to set up your home 
> machine to have dyndns and enable SSH.  You can then just ssh into your 
> home machine, and use org-mode that way too.  I've tried this quite a bit 
> as well, and am kinda at a crossroads on which I like the most yet...
> 
> I hope this helps.
> 
Thanks David

your method looks similar to how I'm managing my init files - a single repo on
my usb key (in your case a web server) which I push to and pull from.

My current problem is more complicated (to me!) than that. I'm having difficulty
explaining it though.

On 'home' I pull changes from 'remote' at //repo.or.cz.

What I would like to do then is either:

1. change 'remote' to be my usb key and push changes to that, or
2. use 'home' as 'remote' from my usb key and pull changes.

Then I'd probably use the same strategy when I got to my 'work' laptop - either
the usb key is 'remote', or 'work' becomes 'remote' from POV of the usb.

More like this:

 repo.or.cz <-> Home <-> USB <-> Work

If it made it easier, I *could* do:

 repo.or.cz <-> USB -> Home
                   \ -> Work

But that may be even more complicated!

Paul

  reply	other threads:[~2009-02-25 17:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-25 16:38 Using Git to update more than one machine (one without network access) Paul Mead
2009-02-25 16:58 ` David Thole
2009-02-25 17:12   ` Paul Mead [this message]
2009-02-25 17:10 ` Nick Dokos
2009-02-25 17:23   ` Paul Mead
2009-02-25 17:41 ` Ian Barton
2009-02-25 18:09   ` Paul Mead
2009-02-25 18:19   ` Paul Mead
2009-02-25 18:41     ` Bernt Hansen
2009-02-25 18:56       ` Paul Mead
2009-02-25 19:31         ` Bernt Hansen
2009-02-25 21:12           ` Paul Mead

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.20090225T170341-347@post.gmane.org \
    --to=paul.d.mead@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).