Re: about svk

Chia-liang Kao said:
> I didn't ignore any request about the name change; if you have seen the
> README, I explicitly mention that: "all things are subject to change,
> including project name, binary name, perl module namespaces, depot
> spec, etc."
>
> The point about potential confusion was taken, altough I have never used
> nor even seen bitkeeper myself.

BitKeeper is popular enough that even the Linux Kernal has been using it for a
while now. Unless that's recently changed.

> I just can't make naming stop myself from doing interesting real works.

>> To be utterly, *completely* legally safe here: -1 on any of those
>> custom props appearing in our tree until the name is changed. (Not
>> the name of the prop, but the name of the software that produced them,
>> that is. To store the props might be taken as an implicit endorsement
>> of their source.)

SubversionDistributor?

And svd?

I mean, isn't that really what it is?

It's really not a keeper of anything is it.

-- 
Shamim Islam
BA BS
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org