Support patterns-from #49
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#49
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Borg has an option
patterns-from
that lets you specify file with include/exclude patterns. Could borgmatic have it also? Or could borgmatic have any option to let you pass any option you want toborg create
?borgmatic already supports "native"
exclude_patterns
andexclude_from
config options. Do you want to use Borg'spatterns-from
because you also need to specify includes and not just excludes? The Borg feature is marked experimental, so I haven't implemented it yet, but I can imagine why it'd be useful. Out of curiosity, what do you want to use it for?Thanks!
I'm trying to create something to ignore files that are ignored in
.gitignore
files found in backup files. So, I have these lines in my config:It is quick and dirty, but it works. The only problem is that I have to ignore not-exclude patterns from
.gitignore
as there is no way to specify these in--exclude-from
. That's why I need--patterns-from
.Makes sense.. Thanks for clarifying the need and including the work-around example!
Just implemented this in master via new
patterns_from
andpatterns
configuration options in borgmatic. It'll be part of the next release. I'll be interested to hear how it works out for your use case.borgmatic 1.1.13 was just released with this.
Well, borgmatic fails with
I suppose the problem is that the argument name is
patterns-from
, notpattern-from
.There are 6 instances of
pattern-from
inb8f6bab12d
My bad, will fix!
Okay, fixed and released in borgmatic 1.1.14.