![]() Does git create temporary files as part of the transfer? Also, I was watching the SparkleShare process in Activity Monitor and its memory usage was minimal. ![]() One thing that might be at fault here is that I'm low on HD space on the machine. git status Common options Ignoring Files Untracked files can be of two types: ones that have not been added and committed to the project and the ones that are binaries like. If I move the files out of the SparkleShare folder, and re-run SparkleShare, it won't crash. Usage The git status lists which files are staged, unstaged, and untracked. ![]() Unhandled Exception: System.ArgumentException: Commit message must not be null or empty!Īt (System.String message, GitSharp.Author author) in :0Īt (System.String message, GitSharp.Author author) in :0Īt (System.String message) in :0Īt (System.String message) in :0Īt () in :0Īt (System.String path) in :0Īt (System.String folder_path) in :0Īt () in :0Īt () in :0 usr/local/git/bin/git status -porcelain (204.62.14.135)įatal: Out of memory? mmap failed: Cannot allocate memory man git-status helpfully informs us what the -porcelain flag is for: Give the output in an easy-to-parse format for scripts. From the above posts, it would appear that, when git status is run, it calls git status -porcelain. usr/local/git/bin/git ls-remote origin master We divide git into high level ('porcelain') commands and low level ('plumbing') commands. When I issue a restart, it seems to fix the issue, temporarily. ![]() Upon opening SparkleShare from the command line, I get the standard messages:ġ5:25:30] /usr/local/git/bin/git status -porcelain There is nothing else in the logs except for normal updates, and then 1000s of git status -porcelain commands and they keep on coming at a rate of about 2 a second. With SparkleShare closed, I copied about 45 gigs worth of data which amounted to around 481 files. Just recently set up SparkleShare on my mac (10.6.7) with 8 gigs of ram and have it pointing to a private git server with 800+gigs of free space. ![]()
0 Comments
Leave a Reply. |