2018/05/22 ver 188.8.131.52
Last Updated May 21, 2018 Version 184.108.40.206
The documentation on options in the section below are sorted in alphabetical order.
--deeppathdelete--deletedelete verylong path
need to delete such paths or files.
ln --deeppathdelete x:\DeepPath\file
But there are some fascinating cases turning up, when one takes a closer look:
Creating and keeping many Delorean Copies in a Delorean Set is something which is fairly simple, and even when it comes
to deleting a specific Delorean Copy from a Delorean Set it is easy. Simply press delete in Explorer, or use the --deeppathdelete
option from ln.exe:
Wait! It is that easy if a Delorean Copy contains no files with ReadOnly attributes. Otherwise it's getting sophisticated:
A Source was used to create three successive Delorean Copies: Bkp1,Bkp2,Bkp3. File B is ReadOnly in the Source and
in all Delorean Copies. So far so good.
When it comes to delete Bkp2 the Readonly attribute of Bkp2/B has to be removed, otherwise deletion is impossible.
Due to the fact that all siblings of a hardlink share the same attribute and the same date, the readonly attributes of Bkp1/B and Bkp3/B are also
'changed'. This is shown via the blue dotted lines. Called it 'Hardlink Attribute Teleportation'
This results now in having a different attribute in Bkp1/B and Bkp3/B than in Source/B. This is shown via the grey dotted line.
A fourth delorean copy with Source and Bkp3 as Backup to Bkp4 is created.
Since the attributes of Bkp3/B and Source/B are different, the file Bkp4/B was copied over freshly from Source/B. So there is no
hardlink between Bkp3/B and Bkp4/B, which is shown with the light red dotted line, and which is the basic problem.
2016/12/12 ver 220.127.116.11