| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
Regression introduced in:
commit c23422388b975f13867457c86c78361dfdf8036e
Author: Tomas Herman <tomas.herman@wikidi.com>
Date: Tue Apr 23 11:59:38 2013 +0200
Added support for pulling only a subset of files.
Reported-by: Nikola Kovacs <nikola.kovacs@gmail.com>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
if a symlink has a length of self.magiclen git-fat would crash
because it could not read the file
|
|\
| |
| |
| |
| | |
* 'symlinks-in-index-filter' of github:chhitz/git-fat:
ignore symbolic links during index-filter
|
| |
| |
| |
| |
| | |
symbolic links should not be handled by git-fat even if
their name match the filelist
|
| | |
|
|/
|
|
| |
patch from https://gist.github.com/edufelipe/1027906
|
|
|
|
|
|
|
|
|
|
| |
tempfile.mkstemp() creates a file with mode 0600 by default, which after
pushing, prevents others from accessing the shared object store.
Instead, use 0444 (as with git-native objects) and respect umask so that
pushed objects will be readable with default configuration.
Noticed-by: Ashok Argent-Katwala <ashok@freshbooks.com>
Comments-by: Owen Jacobson <owen.jacobson@grimoire.ca>
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
https://github.com/michaelcontento/git-fat (PR #12)
This does not resolve all unicode file name issues. We have at least
these issues:
1. Filenames sometimes become command-line arguments, which we'd rather
avoid because it forces us to decode/encode (on Windows). This can
be fixed by systematically using '--stdin' options.
2. We still use 'git ls-files -s' in cmd_index_filter. It should also
learn to use the -z option, but unfortunately, Python doesn't have
convenient line processing for NUL-delimited streams so we have to
write something like difftreez_reader to do that properly.
* 'pull-with-unicode-filenames' of https://github.com/michaelcontento/git-fat:
fix "git fat pull" for fancy named files
[Normalized quoting style in merge.]
|
|/
|
|
|
|
| |
just add "-z" to "git ls-files" and split the string at the null byte instead of
newline. now we get the original name back from git and the os module should
handle the communication with the filesystem (but I haven't checked this!).
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This writes a .gitattributes file for every commit in the history,
appending rules for all the now-managed fat files.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
git rev-list --objects has a second field for objects other than
blobs (like trees), so they cannot be filtered out a priori.
|
| |
|
| |
|
| |
|
|
|
|
| |
bare repository.
|
| |
|
|
|
|
|
|
|
| |
subprocess.communicate() cannot be used with large files because it is a
fully-synchronous interface. Since there is no stream/generator/coroutine
support in subprocess.communicate, we have to roll the line iterator ourselves,
putting the filter in its own thread.
|
|
|
|
| |
not yet exist
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The new code can still smudge from the old format, but the clean filter
will always produce the new format, causing Git to complain. This means
that as soon as you check out an old version, git will think there are
local modifications. There is a backdoor, however. If you set
GIT_FAT_VERSION=1 while interacting with checkouts of old versions, the
old behavior will be recovered. Just don't forget to unset it when
moving back to the latest version. To checkout across versions, use
--force.
You can upgrade the repository (without changing the fat object store)
by committing the new cleaned objects.
|
|
|
|
|
|
|
|
| |
git fat init now checks whether the filter.fat section is already
defined.
Manage .gitfat using git-config instead of Python ConfigParser, which
has different syntax support.
|
|
|
|
| |
use --all to get all branches
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
* Verbosity control
* Automatically update working tree
* Identify orphan files in filter-clean and pass through so they don't
show up as suprious diffs.
|
|
|