add note to git-annex-log man page about when information is not available

This commit is contained in:
Joey Hess 2021-04-23 14:53:38 -04:00
parent bfa2db9222
commit 34c2d13dce
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 11 additions and 16 deletions

View file

@ -8,11 +8,19 @@ git annex log `[path ...]`
# DESCRIPTION # DESCRIPTION
Displays the location log for the specified file or files, Displays the location log for the specified file or files, showing each
showing each repository they were added to ("+") and removed from ("-"). repository they were added to ("+") and removed from ("-"). Note that the
Note that the location log is for the particular file contents currently at these paths, location log is for the particular file contents currently at these paths,
not for any different content that was there in earlier commits. not for any different content that was there in earlier commits.
This displays information from the history of the git-annex branch. Several
things can prevent that information being available to display. When
[[git-annex-dead]] and [[git-annex-forget]] are used, old historical
data gets cleared from the branch. When annex.private or
remote.name.annex-private is configured, git-annex does not write
information to the branch at all. And when annex.alwayscommit is set to
false, information may not have been committed to the branch yet.
# OPTIONS # OPTIONS
* `--since=date`, `--after=date`, `--until=date`, `--before=date`, `--max-count=N` * `--since=date`, `--after=date`, `--until=date`, `--before=date`, `--max-count=N`

View file

@ -145,19 +145,6 @@ all reads followed by writes do go via Annex.Branch.change, so Annex.Branch.get
can just concacenate the two without worrying about it leaking back out in a can just concacenate the two without worrying about it leaking back out in a
later write. later write.
> Implementing this is in progress, in the `hiddenannex` branch.
>
> Got the separate journal mostly working. No separate index yet.
> No way to configure what repo is hidden yet. --[[Joey]]
>
> Implementation notes:
>
> * [[bugs/git-annex_branch_caching_bug]] was a problem, now fixed.
> * Any other similar direct accesses of the branch, not going through
> Annex.Branch, also need to be fixed (and may be missing journal files
> already?) Most fixed now. Command.Log behavior needs to be
> investigated still.
## networks of hidden repos ## networks of hidden repos
There are a lot of complications involving using hidden repos as remotes. There are a lot of complications involving using hidden repos as remotes.