emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ian Barton <lists@manor-farm.org>
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:41:22 +0000	[thread overview]
Message-ID: <49A582C2.3090407@manor-farm.org> (raw)
In-Reply-To: <loom.20090225T152333-29@post.gmane.org>

> I use a repo on a usb drive to keep my emacs init files in sync, but have
> absolutely no idea how to do this for my org-mode files. In essence, I'm trying
> to first pull changes from //repo.or.cz to my laptop, and then either have a
> second repo on the usb drive which I can pull changes onto, or pull from the
> laptop to the usb.
> Then I have to somehow get the work laptop to pull changes from the usb.
> Am I asking for too much here? I want to avoid all the downloading and unzipping
> where possible.
One way to accomplish this would be to create a "branch" on your usb 
stick. Not sure if the terminology is correct here, as I use bzr rather 
than git.

You can then create branches on your home computer and your work 
computer using the usb stick as a repo. So your workflow would be

Use git clone to create a repo on your usb stick.

Pull changes from Carsten' git repo to your usb stick.

Pull changes from your usb stick to both your work and home computers. 
In other words your usb stick is your own master repo.

I am not a VCS guru, so there is probably a simpler way:)


  parent reply	other threads:[~2009-02-25 17:41 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
2009-02-25 17:10 ` Nick Dokos
2009-02-25 17:23   ` Paul Mead
2009-02-25 17:41 ` Ian Barton [this message]
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:

  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=49A582C2.3090407@manor-farm.org \
    --to=lists@manor-farm.org \
    --cc=emacs-orgmode@gnu.org \


* 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


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).