@@ -316,6 +316,11 @@ This value is true by default in a repository that has
a working directory associated with it, and false by
default in a bare repository.
+core.backupLog::
+ If true, many commands will keep backup content in object database
+ before they modify some file. See linkgit:git-backup-log[1] for more
+ information.
+
core.repositoryFormatVersion::
Internal variable identifying the repository format and layout
version.
new file mode 100644
@@ -0,0 +1,107 @@
+git-backup-log(1)
+=================
+
+NAME
+----
+git-backup-log - Manage backup log files
+
+
+SYNOPSIS
+--------
+[verse]
+'git backup-log' [--id=<id> | --path=<path>] log [<rev-options>] [[--] <path>...]
+'git backup-log' [--id=<id> | --path=<path>] cat [--before] [--hash] <change-id> <path>
+'git backup-log' [--id=<id> | --path=<path>] diff [<diff-options>] <change-id>
+'git backup-log' [--id=<id> | --path=<path>] prune [--expire=<time>]
+'git backup-log' [--id=<id> | --path=<path>] update <path> <old-hash> <new-hash>
+
+DESCRIPTION
+-----------
+Backup log records changes of certain files in the object database so
+that if some file is overwritten by accident, you could still get the
+original content back.
+
+Backup log is enabled by setting core.backupLog to true and the
+following commands will save backups:
+
+- linkgit:git-add[1] keeps all index changes. File removal is not
+ recorded.
+- linkgit:git-commit[1] keep all index changes in `-a` or partial
+ commit mode.
+- linkgit:git-apply[1] and linkgit:git-update-index[1] will keep
+ changes if `--keep-backup` is specified
+- Changes of `$GIT_DIR/config` made by `git config --edit` are kept.
+- Deleted reflogs are kept. References from this deleted reflog will
+ not be kept at the next garbage collection though. This is mostly
+ meant to immediately undo an accidental branch deletion.
+- linkgit:git-checkout[1] when switching branches and
+ linkgit:git-merge[1] will make a backup before overwriting
+ ignored files.
+- linkgit:git-checkout[1] with `--force`, linkgit:git-reset[1] with
+ `--hard` or linkgit:git-am[1] and linkgit:git-rebase[1] with
+ `--skip` or `--abort` will make a backup before overwriting non
+ up-to-date files.
+
+Backups are split in three groups, changes related in the index, in
+working directory or in $GIT_DIR. These can be selected with `--id`
+parameter as `index`, `worktree` and `gitdir` respectively.
+Alternatively file path of these are `$GIT_DIR/index.bkl`,
+`$GIT_DIR/worktree.bkl` and `$GIT_DIR/common/gitdir.bkl` which could
+be specified with `--path`
+
+This command is split into subcommands:
+
+update::
+ Add a new change associated with `<path>` from `<old-hash>` to
+ `<new-hash>` to the selected backup log file. `<path>` must be
+ normalized.
+
+log::
+ View the selected backup log (optionally filtered by pathspec).
+ By default, the diff of the change is shown.
+
+cat::
+ Output the file content or their object name of a specific
+ change.
+
+diff::
+ Output the diff of a specific change.
+
+prune::
+ Prune the backup log, delete updates older than a specific
+ time or invalid entries. The actual backup content is still in
+ the object database and may need to be pruned separatedly.
+
+OPTIONS
+-------
+
+--id=<id>::
+ The name of the the backup log file. Supported names are
+ `index`, `worktree` and `gitdir`.
+
+--path=<path>::
+ The path of a backup log file.
+
+--before::
+ Show the version before the change instead. This is most
+ useful when the change is a file deletion.
+
+--hash::
+ Show the object name instead of content.
+
+--expire=<time>::
+ The cutoff time for pruning backup log. The default is three
+ months ago.
+
+<path>::
+ The path of the file where the change is made.
+
+<old-hash>::
+ The blob hash of the content before the change.
+
+<old-hash>::
+ The blob hash of the content after the change.
+
+GIT
+---
+Part of the linkgit:git[1] suite
A reflog file records changes of a certain ref over time. A backup log file does a similar job, but it records changes of some files over time. This is the main idea of it. This is added so that we can support undoing certain changes. For example, if you have carefully prepared your index with "git add -p" then accidentally do "git commit -a", your well crafted index is lost with no easy way to recover it. We could go the other way and make "git commit -a" complain loudly, but that has other bad side effects, the big one is we may complain too loudly at the wrong time and too often. This "do the right things (most of the time) but allow the user to undo when we get it wrong" approach seems more inline with how git handles other things. The current plan is to have three backup log files: - $GIT_DIR/index.bkl contains "interesting" changes made in the index. - $GIT_DIR/worktree.bkl contains "interesting" changes made in worktree. - $GIT_DIR/common/gitdir.bkl contains changes made in other files inside $GIT_DIR such as config, those in info/ directory, or reflog file deletion (aka the mystical reflog graveyard) All these only record "interesting" changes which will be defined later. But a few examples of them are: "git add -p" is interesting, but "git reset HEAD" is not. Similarly changes made in $GIT_DIR/config are usually interesting. This patch does none of that! It adds a new man page for a new plumbing command "git backup-log" which does show what this functionality looks like. Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com> --- Documentation/config/core.txt | 5 ++ Documentation/git-backup-log.txt | 107 +++++++++++++++++++++++++++++++ 2 files changed, 112 insertions(+) create mode 100644 Documentation/git-backup-log.txt