git
The file will have its original line endings in your working directory. warning: LF will be replaced by CRLF in ...
Generally in the Unix your end of a line is always represented with the line feed (LF). And in windows the line is always represented with the carriage return (CR) and your end of line (LF) thus (CRLF). So when you have code from git that was uploaded by the unix system then it will only have the LF.
If you want to turn warning off then you can do it by typing a below command in your git command line
git config --global pack.windowMemory "100m"
git config --global pack.packSizeLimit "100m"
git config --global pack.threads "1"Setting pack.threads "10" fixed it for me
Meaning: GIT - old mode 100755 new mode 100644
These changes mean that metadata about your file changed, however the content of your file did not. In order to ignore these changes, please run one of the the following sets of commands.
git config --unset core.filemode
git config --global core.filemode falseGit: fatal: unable to create threaded lstat
If the resource limit can't be removed by the hosting provider, you could consider using git config to disable preloading of the index (threaded lstat).
git config core.preloadIndex falseIf you need that setting when cloning the initial repository, then you will need to set it globally.
git config --global core.preloadIndex falsegit status - list last modified date
git status -s | while read mode file; do echo $mode $file $(stat -c %y $file); doneChanging git commit message after push
git commit --amend -m "New commit message"and then
git push --force origin <BRANCH-NAME>Changing a commit message
git commit --amendgit-ftp
# Setup
git config git-ftp.url "ftp://ftp.example.net:21/public_html"
git config git-ftp.user "ftp-user"
git config git-ftp.password "secr3t"
# Upload all files
git ftp init
# Or if the files are already there
git ftp catchup
# Work and deploy
echo "new content" >> index.txt
git commit index.txt -m "Add new content"
git ftp push
# 1 file to sync:
# [1 of 1] Buffered for upload 'index.txt'.
# Uploading ...
# Last deployment changed to ded01b27e5c785fb251150805308d3d0f8117387.
Find big files on git repo
git rev-list master | while read rev; do git ls-tree -lr $rev | cut -c54- | grep -v '^ '; done | sort -u | perl -e ' while (<>) { chomp; @stuff=split("\t"); $sums{$stuff[1]} += $stuff[0]; } print "$sums{$_} $_\n" for (keys %sums);' | sort -rn >> large_files.txtGit commit all deleted files
$ git add -uFrom man git-add
-u, --update
Only match <filepattern> against already tracked files in the index rather than the working tree. That means that it will
never stage new files, but that it will stage modified new contents of tracked files and that it will remove files from the
index if the corresponding files in the working tree have been removed.
