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

Please review my changes on jdsu-ger against your master #39

Open
wants to merge 13 commits into
base: master
Choose a base branch
from

Conversation

ozkandikmen-work
Copy link

Quick summary of my changes:

  • I have implemented a fine grained push mechanism. It is based on a new configuration parameter, 'local' (similar to 'remote', in .gitfat), and the use of sym link vs files. If a file system does not support sym links, git-fat will still work, however, it won't offer the same advantage. I'd like to hear your opinion on that. It's been working great for us over here.
  • I have done bunch of enhancements - mostly minor, but some major as well such as the one in referenced_objects.
  • 0-byte files are handled properly as well.

…JDSU work setup. We do not want it to be 'accidentially' executed.
Completed the removal of the gc function - had forgotten to take the cmd out of the list of available commands in the previous commit.
…lemented. Thus, it is no longer

  necessary for git-fat to run rsync on the entire content of .git/fat/objects => faster pushes.
- Enhanced smudge filter to retrieve only what HEAD references (no history) => faster update of
  your tree. As a result, you don't have to run 'git fat pull' which would pull in all fat files
  that HEAD (including history) references. You can for instance just do 'git pull' and the smudge
  filter will do the rest. Note: Not doing 'git fat pull' up front comes with a performance hit
  if ssh is set up to run rsync over because each new fat file the smudge filter needs requires
  a new ssh connection to be established.
- local, if set up appropriately, allows sharing of fat files across multiple clones of the same
  repo => more efficient use of disk space.
- Also now running 'git push' from within 'git fat push' in order to streamline push operation.
  'git push' is executed *after* fat files are pushed successfully.
- Also now running 'git pull' from within 'git fat pull' in order to streamline pull operation.
  'git pull' is executed *before* fat files are pulled.
…l' to automatically update already initialized repos to the latest format
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

Successfully merging this pull request may close these issues.

1 participant