<poolie> i think that's a sore point for jml, and some other users
<poolie> vila: i think most ignored files are safe to delete
<poolie> i think most of the time that's what people want
<poolie> possibly the other cases could be handled by moving them to either a backup file in a parent directory
<poolie> or say .bzr/trash
<spiv> poolie: I actually think a dir in the working tree root, rather than in .bzr, would be good
<spiv> I'm not sure that hidden-by-default is even necessary, why hide the junk? I don't, though...
There are still some points to address like:
- How to name the files moved in the trash.
We can remove the parent part of the path and add a ~n suffix not yet used there.
That allows one to list either by name or by date to find a backup more quickly
- Maintain a file in append more listing full path/backup path associations,
- Have a trash specific filter saying things like: don't even think about keeping .pyc files !
<poolie> i think that's a sore point for jml, and some other users
<poolie> vila: i think most ignored files are safe to delete
<poolie> i think most of the time that's what people want
<poolie> possibly the other cases could be handled by moving them to either a backup file in a parent directory
<poolie> or say .bzr/trash
<spiv> poolie: I actually think a dir in the working tree root, rather than in .bzr, would be good
<spiv> I'm not sure that hidden-by-default is even necessary, why hide the junk? I don't, though...
There are still some points to address like:
- How to name the files moved in the trash.
We can remove the parent part of the path and add a ~n suffix not yet used there.
That allows one to list either by name or by date to find a backup more quickly
- Maintain a file in append more listing full path/backup path associations,
- Have a trash specific filter saying things like: don't even think about keeping .pyc files !