https://stackoverflow.com/questions/3240881/git-can-i-suppress-listing-of-modified-content-dirty-submodule-entries-in-sta
So the trick is to adapt .gitmodules, not .gitignore. Merlijn On 31 January 2014 09:56, Mpaa <[email protected]> wrote: > Hi. > > Is there a way to avoid having these to file to always show up as > non-staged? > > $ git status > # On branch cat > # Changes not staged for commit: > # (use "git add <file>..." to update what will be committed) > # (use "git checkout -- <file>..." to discard changes in working > directory) > # > # modified: externals/httplib2 (new commits) > # modified: scripts/i18n (new commits) > > I found this suggestion online (can't remember where): > Some files in a repository, which are versioned (i.e. they can't be > git-ignored), are often changed, > but rarely committed. Usually these are various local configuration files > that are edited, > but should never be committed upstream. > > Git lets you ignore those files by assuming they are unchanged. This is > done by running the > git update-index --assume-unchanged path/to/file.txt > > but it is not a permanent solution. > > Bye > Mpaa > > _______________________________________________ > Pywikipedia-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l > >
_______________________________________________ Pywikipedia-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
