P.Marek wrote: > Hello everybody! > > I'd like to ask about some behaviour that FSVS should show. > > Please assume this directory tree: > A/ > file > B/ > file > and a symlink > C -> A > > Now this gets committed, and the "file"s change their data; and the symlink > points to B. > > What should a > fsvs ci C/file > do? > > 1) Give an error, because C is not a directory > 2) Commit B/file (and nothing else), because this *target* was chosen > 3) Commit C as pointing to B now > 4) 2+3 together > > I'm not sure what the right behaviour is ... all of these variants have some > sunny side. > > Any ideas? Opinions? > Thanks in advance.
IMHO 4 is correct (2 + 3). It is consistent with how fsvs behaves when you say fsvs ci a/b/c/file and a b or c have metadata modification on them (such modifications get committed). C being a symlink, not a "symlink to X" should get its data/metadata change committed as well. Cheers ------------------------------------------------------ http://fsvs.tigris.org/ds/viewMessage.do?dsForumId=3928&dsMessageId=1878431 To unsubscribe from this discussion, e-mail: [[email protected]].
