Git

Search results for backup

  1. git-mergetool

    /docs/git-mergetool

    Defaults to `true` (i.e. keep the backup files). mergetool.keepTemporaries:: When invoking a custom merge tool, Git uses a set of temporary files to pass to the tool.

  2. git-prune-packed

    /docs/git-prune-packed

    Packs are used to reduce the load on mirror systems, backup engines, disk storage, etc.

  3. git-repack

    /docs/git-repack

    Packs are used to reduce the load on mirror systems, backup engines, disk storage, etc.

  4. git-filter-branch

    /docs/git-filter-branch

    This is a very destructive approach, so *make a backup* or go back to cloning it. You have been warned.

  5. gitignore

    /docs/gitignore

    ., backup or temporary files generated by the user's editor of choice) generally go into a file specified by `core.excludesFile` in the user's `~/.gitconfig`.

  6. git-cvsserver

    /docs/git-cvsserver

    So if you have to fully or partially (from old backup) regenerate the database, you should be suspicious of pre-existing CVS sandboxes.

  7. git-update-index

    /docs/git-update-index

    It can be useful when the inode change time is regularly modified by something outside Git (file system crawlers and backup systems use ctime for marking files processed) (see linkgit:git-config[1]).

  8. git-config

    /docs/git-config

    If false, the ctime differences between the index and the working tree are ignored; useful when the inode change time is regularly modified by something outside Git (file system crawlers and some backup

  9. user-manual

    /docs/user-manual

    This typically includes files generated by a build process or temporary backup files made by your editor. Of course, 'not' tracking files with Git is just a matter of 'not' calling `git add` on them.

scroll-to-top