[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Feature request: Vizualization of 'fsvs' properties.

From: Ph. Marek <philipp_at_marek.priv.at>
Date: Sat, 6 Sep 2008 15:10:01 +0000 (UTC)

Stefan Küng <tortoisesvn <at> gmail.com> writes:
> Ph. Marek wrote:
...
> > and B): because of *compatibility*. If you wrote a new OS, would you call
> > the function that's used to open files "open", or would you name
> > it "GetHandleForAFile"?
> >
> > There've been *existing users* for these properties. Changing them would
> > have broken their data.
> >
> > That's* not nice.
>
> The svn:log property is documented as an *internal* property for
> Subversion, not to be used directly by other applications. The only way
> to use those is via the Subversion API.
> Those who think they can do whatever they want with internal data (like
> you) will lead to them having broken applications.
>
> Don't blame others for not being nice if you're not even willing to
> follow their rules.
You're missing the point. Rather than "just" inventing a new name for the
properties (and breaking all existing repositories for all users) I used the
(already registered) name and meaning.
 
It's about the users, and compatibility with their data.

That's what I meant about using UTF8 - that's an existing standard, which
(most) editors know how to handle.

If you invent new names for existing things (like I meant for "open"
vs. "GetHandleForAFile"), you'll cause people trying to use your OS more work -
because they have to get some compatibility layer for their programs, or change
*every one* of them.

And once again - IMO I followed the rules. Something developed for subversion
used the namespace "svn:" (naturally!); that it wasn't accepted is not my
fault.
But I had to take care for the existing users.

> >>> Did you never use a hex-editor on some 3rd party programs?
> >> I do all the time.
> > So you do? Why? Because if I read you correctly that's not the right way,
> > is it? Why do you do this? For your private use?
>
> Can you explain why using a HEX-Editor is 'not the right way'? You have
> no idea what I'm using those for.
> I guess for you the only way to use a hex-editor is to hack another
> application...
Yes, it is.

If I've got the source, I can re-compile.
If I don't have the source, but the vendor is listening, I can get a changed
binary.

So you're right - I use a hex-editor for hacking.

But you didn't answer the question - why do *you* use it, if the proper way is
to get everything the official, planned, documented way?

Regards,

Phil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: dev-help_at_tortoisesvn.tigris.org
Received on 2008-09-06 17:20:08 CEST

This is an archived mail posted to the TortoiseSVN Dev mailing list.