|
From: Lark <la...@fe...> - 2000-07-12 16:43:44
|
> Lark, please don't sign me up for write access yet. I've never used > CVS before, so I'd rather wait until I learn how it works and what > I'm doing with it. I'd really hate to be playing around with it and > accidently do something that nukes all the code. =) If you never "commit" anything, you can't break anything. :-) It's your choice, but I'd set you up with it just so it's ready when you need it. > From the readme: > However, what you are not permitted to do is to redistribute the > source as "DSC Sample Code" after having made changes. If you're > going to redistribute the source, we require that you make it clear > in the source that the code was descended from Apple Sample Code, but > that you've made changes. > > It sounds to me that it would be ok to redistribute it since it > hasn't been modified. All of the files in the package do have the > Apple Source Code info at the top. If that's left in, it should be > ok. That sounds reasonable. I'll try to contact the author, just to make sure. > I have no objections as long as it'll make it easier for the overall > project. Importing the XML isn't difficult. I just wouldn't want to > do it if its going to cause problems for someone or somewhere. The biggest difference is that since it's text, you can have CW or BBEdit compare versions and highlight differences, so it's easy to see what has changed, if you need to. Also, with binary files, CVS always replaces the whole file with a new version since it cannot create binary diffs; using XML allows it to do that. (Too bad there isn't a text form for the .rsrc and .ppob files as well.) > P.S. Lark, is it possible to set the mail server so that the reply > address is to the list and not the person who sent it? I've already > sent out a couple messages to just the sender on accident. I think I've changed it. Let me know if it does/doesn't work. Lark |