follow symlinks (2)

It is utterly pointless to argue here. You guys are hell-bent for having
special files in repositories so you can abuse subversion for things
that rsync or other backup solutions were made for and which are clearly
not in the focus of a version control software anymore.

On the other side: To follow symbolic links to store the actual file in
the repository seems /debatable/ to you. Incredibly stupid.

But that's okay. It is your choice.

So I will extend bindfs to hide not just hard links but also symbolic
links. I will probably release a patch.

This will solve the same problem with git too.

Too bad there is no sense for "choice" anymore. "Choice" made the
difference in the past.

Maybe someone will come and tell me, again, how "choice" is a bad thing
because it might confuse the 08/15-Users
that Linux is so desperate to attract in recent years. Together with the
malicious software that follows such an
audience. The ultimate goal is to reinvent Windows badly until everyone
has switched.

But whatever. If a modified bindfs is necessary to make subversion an
alternative to CVS, then so it shall be.

An actual developer who has the authority here to add the option to the
configure script might follow this thread and think by himself:

"Why bother. It is just a version control program and there is so much
else to do."

And I am thinking exactly the same after reading your pinheaded weasel
replies.

Unsubscribed before I get cancer or permanent brain damage from reading
your passive-aggressive bullshit.
Received on 2013-11-07 20:35:02 CET