-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Git Log as History #20
Comments
I hope I understand where you're trying to go here… Perhaps it would be an idea to store the You don't mean using git for computing / keeping all the changes (thus committing all files to git) and then pushing the entire git repository over rsync, right? I think that would make the entire script moreless useless. Please let me know :) Edit: I hope I don't sound like I'm dismissing your idea upfront, because I'm not. Pleas know I really appreciate your input! |
I'm not referring to storing any files in git. Just thinking there might be a way to add a means of exploring what has been there historically, even after we inevitably overwrite things. More of a sanity check: "I know that file existed at some point in history even though its not on any of my backups for whatever reason, though not due to any fault of rsync". |
Do note, I think this is scope creep on the tool itself. But I wanted to share the thought. |
It might be a simple as adding |
I had a thought about using
git
on the names of the files as a sort of history of files over time, kept in the root of the backup directory. One might search this to see when a file has been removed permanently or other such things.The text was updated successfully, but these errors were encountered: