Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Environment variables in .gitfat not working correctly #49

Open
marcuslvgrn opened this issue Aug 21, 2014 · 1 comment
Open

Environment variables in .gitfat not working correctly #49

marcuslvgrn opened this issue Aug 21, 2014 · 1 comment

Comments

@marcuslvgrn
Copy link

I'm trying to use an environment variable in the .gitfat file, like
-> cat .gitfat
[rsync]
remote = localhost:$GIT_FAT_DIR

and

-> echo $GIT_FAT_DIR
/tmp/gitfat

But it gives the result

-> git fat pull
Pulling from localhost:$GIT_FAT_DIR
Executing: rsync --progress --ignore-existing --from0 --files-from=- localhost:$GIT_FAT_DIR/ /tmp/repo/.git/fat/objects/
GIT_FAT_DIR: Undefined variable.
rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
rsync error: error in rsync protocol data stream (code 12) at io.c(600) [receiver=3.0.6]

Is it possible to use a variable there, and if so, how do you write it?

@jedbrown
Copy link
Owner

Marcus Lövgren [email protected] writes:

I'm trying to use an environment variable in the .gitfat file, like
-> cat .gitfat
[rsync]
remote = localhost:$GIT_FAT_DIR

This is not supported by git config and I'm not interested in supporting
it (environment variables cause too many problems in my opinion). I
would like to add a local git config (e.g., stored in .git/config) that
could be used to override .gitfat on a per-repository basis. Ideally
this change would come with the ability to name remotes.

kbrewersq pushed a commit to kbrewersq/git-fat that referenced this issue May 21, 2021
kbrewersq pushed a commit to kbrewersq/git-fat that referenced this issue May 21, 2021
resolves jedbrown#49 to make 'git fat pull' compatible with a sparse-checkout re...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants