From: Bernt Hansen <email@example.com>
To: "Alan E. Davis" <firstname.lastname@example.org>
Cc: emacs-orgmode Mailinglist <email@example.com>
Subject: Re: MORE: Using git via USB for personal org dir and other data files
Date: Sat, 28 Feb 2009 23:10:50 -0500 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Alan E. Davis's message of "Sun\, 1 Mar 2009 13\:04\:25 +1000")
"Alan E. Davis" <firstname.lastname@example.org> writes:
> Thank you Bernt (and Sebastian):
I'm just trying to help :)
> I now understand that it is necessary to pull the changes to the alternate tree before pushing. This will make a big
> difference in the future, I believe. It worked as advertized on the /tmp/junk experiment.
> I think the other point I had missed, that would be necessary in an FAQ or tutorial, is that it is necessary to initially
> clone each of the working trees, on each machine, from the bare repo on the USB flash drive. Then it now makes sense to
> me to name that as org.git, to distinguish it as a bare repo. And once the working trees are cloned from there, then the
> org.git on the USB drive is recognized automatically as "origin". That point eluded me. And that git pull will perhaps
> automatically find origin.
git pull and git push use the default remote 'origin' if none is
> Meld is starting to make sense too. Thought it would be nicer to have a tool that would be able to make simple updates
> from two edits on the same file if they don't conflict. Usually, this will not be the case.
> Now, is it useful to use the switches on an ext2 formatted USB drive, as follows?
> $ git clone -l --no-hardlinks --bare . /path/to/usb/stick
I've never used -l --no-hardlinks when creating repos on my usb stuck.
vfat filesystems don't support hard links and you can't make use of
hard links across filesystems.
There is lots of information available from git man pages (ie. git clone
--help) which describes what all of the options do.
next prev parent reply other threads:[~2009-03-01 4:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-28 5:11 Alan E. Davis
2009-02-28 11:58 ` Ian Barton
2009-02-28 13:32 ` Bernt Hansen
2009-02-28 20:00 ` Sebastian Rose
2009-02-28 20:01 ` Bernt Hansen
2009-02-28 22:07 ` Sebastian Rose
2009-03-01 1:10 ` Sebastian Rose
[not found] ` <email@example.com>
[not found] ` <87zlg655pk.fsf@kassiopeya.MSHEIMNETZ>
[not found] ` <firstname.lastname@example.org>
2009-03-01 3:04 ` Alan E. Davis
2009-03-01 3:05 ` Alan E. Davis
2009-03-01 4:57 ` Bernt Hansen
2009-03-01 4:10 ` Bernt Hansen [this message]
2009-03-01 15:07 ` Sebastian Rose
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 \
* 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).