
* Fix minor FD leak in journal code. Closes: #754608 * direct: Fix handling of case where a work tree subdirectory cannot be written to due to permissions. * migrate: Avoid re-checksumming when migrating from hashE to hash backend. * uninit: Avoid failing final removal in some direct mode repositories due to file modes. * S3: Deal with AWS ACL configurations that do not allow creating or checking the location of a bucket, but only reading and writing content to it. * resolvemerge: New plumbing command that runs the automatic merge conflict resolver. * Deal with change in git 2.0 that made indirect mode merge conflict resolution leave behind old files. * sync: Fix git sync with local git remotes even when they don't have an annex.uuid set. (The assistant already did so.) * Set gcrypt-publish-participants when setting up a gcrypt repository, to avoid unncessary passphrase prompts. This is a security/usability tradeoff. To avoid exposing the gpg key ids who can decrypt the repository, users can unset gcrypt-publish-participants. * Install nautilus hooks even when ~/.local/share/nautilus/ does not yet exist, since it is not automatically created for Gnome 3 users. * Windows: Move .vbs files out of git\bin, to avoid that being in the PATH, which caused some weird breakage. (Thanks, divB) * Windows: Fix locking issue that prevented the webapp starting (since 5.20140707). # imported from the archive
13 lines
723 B
Markdown
13 lines
723 B
Markdown
I periodically move unused files to one of my servers. What I would like to
|
|
do is drop any unused file that has been unused for say more than 6 months?
|
|
I would like to not drop all unused files.
|
|
|
|
> It strikes me that this is quite similar to how git handles deleting
|
|
> stale refs with the reflog. So, if `git annex unused` were changed to
|
|
> also look at the reflog, it would keep all files referred to by all refs
|
|
> in the reflog, until the reflog expires. You could then set reflog expiry
|
|
> to 6 months, and be done.
|
|
>
|
|
> However, I think that many users expect git annex unused to be able to
|
|
> immediately find and remove a file after it's been deleted. So this
|
|
> probably needs to be a configurable behavior. --[[Joey]]
|