Re: followup question to FAQ

"C. Michael Pilato" <cmpilato@collab.net> writes:

> So, I actually gave this idea a shot, and to my surprise, it doesn't
> work. But it doesn't work for non-obvious reasons. I might have
> uncovered a bug here. Watch this space for more.

Yep. It's a bug.

Say two users, Harry and Sally, each checkout working copies of the
HEAD of a project. Harry sets a new property on a file in that
project, and commits. He then decides that Sally's gonna beat him up
for doing that, so he removes the property from the file, and commits
again. Later, Sally updates her working copy, and sees no changes
come down from the server.

None at all.

Not even a no-op change to the file.

In fact, the file's $Rev$ keyword doesn't even change. It's as if
Harry had never touched that file at all.

And that, my fair Subversion users, is what we call a bug.

I have confirmed that the server is doing the right thing. The client
code must be swallowing up the change incorrectly.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 25 17:44:47 2004