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

Re: New Subversion Book Released

From: Michael L Brown <michael.l.brown_at_philips.com>
Date: 2005-05-25 21:25:36 CEST

Mike Brown (Michael.L.Brown@Philips.com)
            Lotus Bloats: Michael L Brown/MSN/MS/PHILIPS
Philips/ADAC, Madison, WI
Desk: 608-288-6969 Fax: 608-298-2101
PMS direct: 164-6969
You design it, I'll build it!

William Nagel <bill.nagel@gmail.com> wrote on 05/24/2005 03:42:18 PM:

> Hi all,
> I'd just like to announce the official release of my new book:
> Subversion Version Control: Using the Subversion Version Control
> System in Development Projects
> It's a fun-filled romp that follows the adventures of a miscreant
> youth as he matures in the deep south...
> Or maybe it's a new Subversion book that looks at how you can get
> more out of integrating Subversion into your development process,
> from the perspectives of the version control newbie, the client user
> (e.g. the software developer), the repository administrator, and the
> project manager.
> I guess you'll just have to buy to book to find out exactly which... :-)

I agree with everything mentioned on the back cover, except:

"This book introduces you to Subversion, a free, open-source version
control system, which is both more powerful and much less complex than
its predecessor CVS."

More powerful, yes. Less complex, nope. As pointed out in previous
postings, our situation with binary files and how not to have them get
affected with svn:keywords property substitution is becoming a real
complex issue for us. With CVS, a single global file contained a list
of files that would automatically get marked with the -kb option,
which kept them from having keywords substituted. Said feature does
not exist with SVN.

Now I have to write a hook script, or more, to do that work for us.
The note mentions that you have hook script examples. Are your examples
to the point that I can use them to figure out what I need to do, i.e.,
check that it is a text file of the type that I would check for and
then set the property? Plus, make sure that the user didn't set the
property by mistake (which we didn't do with CVS)?

Something just came to mind that I didn't think of before... would it
be easier to look for the fact that it is a binary file and make sure
that the proprty isn't set and just set it for all other files? I
have a list of all the binary types that we have, since it is in the
CVS configuration file. Like I said, and another poster agreed with,
using the user's .subversion/config file for doing this is just not

I want to use the KISS principle on the whole process. The more
complex it is, the more prone it is to error.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 25 21:31:46 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.