git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gelonida <gelonida@gmail.com>
To: git@vger.kernel.org
Subject: git clone / git pull to USB memory stick (FAT) and symlinks
Date: Thu, 11 Nov 2010 17:35:17 +0100	[thread overview]
Message-ID: <ibh605$adm$1@dough.gmane.org> (raw)

Hi,

For a given project I'd like to have some USB memory sticks, which I'd
like to keep up to date.

I thought about cloning a remote git repository onto the stick
and performing
- regular pulls in order to update the USB stick
- occasional pushes in orderto publish changes performed on the stick.


Now my questions:


1.) Ignore skip / symlinks
-----------------------------
The git repository might contain symlinks (as it was created on a  linux
host)

Is there any way to perform a git clone / pull and just skip any symlink
in the working directory


2.) Avoiding file permission issues: Is this sufficient
---------------------------------------------------------

I read about some config setting which should avoid problems with
the rather limited file permissions on a FAT file system

git config --add core.fileMode false



3.) Any other special config settings
-----------------------------------------
Are there any other special preparations to be done fi I'd like to
have a non bare git repository on a memory stick.


Thanks for your suggestions

             reply	other threads:[~2010-11-11 16:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-11 16:35 Gelonida [this message]
2010-11-11 17:54 ` git clone / git pull to USB memory stick (FAT) and symlinks Junio C Hamano
2010-11-11 18:03   ` Gelonida
2010-11-11 18:09   ` Gelonida
2010-11-11 18:10   ` Gelonida
2010-11-12 15:06   ` Ferry Huberts
2010-11-12 15:59     ` Santi Béjar

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='ibh605$adm$1@dough.gmane.org' \
    --to=gelonida@gmail.com \
    --cc=git@vger.kernel.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.
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 NNTP newsgroup(s).