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

Re: Unclear: CVS and Subversion repository difference.

From: Miha Vitorovic <mvitorovic_at_nil.si>
Date: 2005-06-17 16:58:28 CEST

Servico Tpd Rodrigo Alfonso Menezes Madera <tpd.madera@telefonica.com.br>
wrote on 17.06.2005 16:02:20:

> So now the problem has it´s cause discovered: I was reluctant to open my
> mind to a new concept. A concept where it´s all related and revision
> numbers don´t help anymore as CVS to tell how a file changed. A concept
> where the repository is a project. And a concept that I didn´t feel
> confortable with.
>
> Yes, It bothers me. I´m with Ron Gilbert on this one. Maybe I have to
> become more familiar with it and (as I always loved to do) stick to the
> standard. But I can´t possibly see the advantage of having my
> "can-be-useful-and-meaningful-release" trasformed into a
> "internal-ignore-me-please" revision.

Try transforming the "internal-ignore-me-please" revision number into a
"build" number or something like that. Then you'll have "version 1.0 build
138", and maybe you'll get that fuzzy warm feeling once again.

Or maybe you can transform your "can-be-useful-and-meaningful-release"
into "I'll-create-a-meaningfull-release-when-it's-really-so" instead of
having a new release every time a developer decides that a more correct
name for his private method "addClient()" would actually be
"createClient()" :-).

Cheers,

---
  Miha Vitorovic
  Inženir v tehničnem področju
  Customer Support Engineer
   NIL Data Communications,  Tivolska cesta 48,  1000 Ljubljana,  Slovenia
   Phone +386 1 4746 500      Fax +386 1 4746 501     http://www.NIL.si
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 17 17:00:49 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.