Raúl Núñez de Arenas Coronado <raulnac@xxxxxxxxx> writes: > ... I was thinking about what git itself > does when ignoring files, especially when dealing with .gitgnore files > in subdirectories, but clearly this needs a different policy, yes. What "git" internally does is the equivalent of using the "--exclude-per-directory" option to honor ".gitignore" in the subdirectories, and in addition use ".git/info/exclude" as another source, pretty much the same way as "--exclude-from" reads it. > What I needed from this command is a way of backing up some ignored > files. These files should not go into the repository, but I'm using > them temporarily for development so it is a good idea to back them up. > I'll just backup the entire repository instead, is not a big deal :)) The current mechanism can be used to list "ignored" files that must be left out of the project (e.g. the most obvious one being object files "*.o") but these "ignored" files are considered "expendable" (i.e. Git is allowed to remove it as needed, e.g., when switching branches and need to make room---if you have an untracked file F that is ignored, checking out a branch that has a file F/G requires the file F to disappear so that a directory can be created there). We have been discussing to extend the mechanism so that we can have "precious" files, which also will be left out of the project (e.g., "git add ." will not add to the index, just like an ignored file) but are not considered "expendable". If file F is "precious": - "git add ." will not add F to the index - "git status" will not say F is left untracked and can be added - "git clean -f" will not remove it. - checking out a branch with a tracked file F/G will *fail*, to prevent the loss of file. No code yet, but the design consensus is almost there. Once it appears, you should be able to say "give me the list of tracked and precious paths---I do not care about ignored ones that are expendable, because they can be recreated mechanically and that is why they are marked ignored", and from such a list of files, you should be able to drive your back-up solution. [jc: cc'ed those who are involved in the "precious" discussion].
