Tomas M: > I think user should be able to specify source and target branches, and > I see no problem in that, if there is no file with the same name in > the middle (in a branch between the source and target branches). > > I would suggest to check existence of the same file on all branches > between source and target, and return error if the same filename > exists in any of the branches. If not exist then lets allow the user > to copy-down freely. The main goal in my mind is to keep consistent > /union. > > But some users may prefer no checking at all, I can't think of any use > case, but the best solution is to do checks by default, and allow user > to specify a parameter to skip the checks, if he knows what is he > doing :) That way you give the power and the responsibility to users > hands.
I see. That was very similar to what I was thinking. - by default, without specifying source/target branches, src is the first branch where the file exist and dst is the next lower writable branch. in this case, of course, the consistency is checked. - when a user specifies the source/target branches, aufs doesn't check the consistency. Reading your first mail, I was going to stop implementing the options to specify the src/dst branches. It was in order to keep the consistency. But I am chaging my mind again, and thinking about another new option "nocheck". - without "nocheck" (default), aufs checks the consistency even if the src/dst are specified. - specifying "nocheck" explicitly, aufs skips the check. this option is just for the users who know what he is doing. Hmm, probably I need to review the design again. J. R. Okajima ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev
