That's beyond me (code it and submit a patch). Is there not a repository
or a way to submit these to those whom where code it and submit a patch
doesn't frighten?
:-)
On Fri, Jul 13, 2012 at 12:53 PM, backu...@kosowsky.org wrote:
Bryan Keadle (.net) wrote at about 10:50:46 -0500 on Monday,
I don't think you will find many people here willing to code and
submit a patch to satisfy your personal feature requests unless they
happen to need it for themselves. The leader/maintainer of BackupPC is
reportedly focusing all his efforts on a complete rewrite. The rest of
us are here as users
I hear you - I'm not expecting people to serve my personal interests.
But this has been such an active and helpful group, I just thought the
suggestion had merit beyond my personal interest and that someone more
familiar with coding would take interest.
I can't wait to be able to contribute back
On Mon, Jul 9, 2012 at 10:50 AM, Bryan Keadle (.net) bkea...@keadle.net wrote:
How might one suggest such an enhancement request - a trial run feature
that would show *WHAT* would get backed up, but not actually backup?
I'm not really sure the concept makes sense across the different
On Sun, Jul 08, 2012 at 09:48:07AM -0500, Bryan Keadle (.net) wrote:
The BackupPC_dump syntax shows to be:
usage: /usr/share/BackupPC/bin/BackupPC_dump [-d] [-e] [-f] [-i] [-F] [-I]
[-v]
But I could not find where these options are defined.
Read the top of the file for the details on what
The BackupPC_dump syntax shows to be:
usage: /usr/share/BackupPC/bin/BackupPC_dump [-d] [-e] [-f] [-i] [-F] [-I]
[-v]
But I could not find where these options are defined.
Also, does this command actually *DO* the backup, or is it just producing a
list of files to be backed up? I'm still trying