Re: Feature request: confirm data loss when renaming folder with ignored files

Said <[email protected]> writes:

> Here's a case study in the importance of 'ignored' files for you....
>
> I have 6TB of photographs on multiple cloned disks, on and off
> location. The bulk of these are camera originals in .DNG format. From
> these I make selections to edit and prepare derivatives for print or
> publication and these are in .psd or .tif formats. When I synchronize
> these disks, I ignore all .DNGs because a) their modification dates
> seem to change whenever I make a clone and disambiguating these is a
> royal PITA (I only have one lifetime after all); and b) it is the PSD
> and TIF files which definitely need to be updated across all
> backups. Eliminating DNGs from synchronization makes this process
> manageable.
>
> The DNGs which I often ignore are some of the most important because
> they are the foundation of the archive and their contents are rarely
> modified without a format change.

Sure, I can see why those files are important.  What I really meant was
"why are you ignoring things *while syncing the containing directory".
Basically I have come to believe that synchronizing home directories is
basically a bad idea.

I keep sources for my dotfiles in a VCS, and generate them.

For files I want synced, I put them in ~/shared/foo, for various values
of foo.  Each has a .replica that lists the machines they are on, and I
have a script do-unison that reads that and runs unison from the hub to
each.

So each path is either synced entirely, or is not part of any sync.  I
use a total of zero ignore directives.


But, everybody does different things, and I am more or less arriving at:

  It is a bug for unison to remove a file, unless that file was recorded
  on both sides and remove on the other.


> Jorge's tale is terrifying to me and, while I haven't been bitten like
> he has, I will definitely be choosing the option to NOT DELETE
> anything without prior examination.

I do not allow automatic behavior.  I read the proposals and then type
y.  (I use the CLI.)

Also, I do not consider unison to be a backup mechanism. I do regular
backups totally separately, not with unison.

-- 
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].