fair enough, <br>
but it is still fun coming up with them!<br>
(I'll stop bugging you now)<br>
<br>
I personaly don't want to use another vcs again, if I have it my way.<br>
<br><br><div><span class="gmail_quote">On 1/8/07, <b class="gmail_sendername">James Henstridge</b> <<a href="mailto:james@jamesh.id.au">james@jamesh.id.au</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 08/01/07, Marius Kruger <<a href="mailto:amanic@gmail.com">amanic@gmail.com</a>> wrote:<br>> === modified 'VCS'<br>> -cvs<br>> -subversion<br>> +bazaar<br><br>There are a few problems with suggestions like this:
<br><br>1. the reader needs to know what CVS and Subversion are in order to<br>understand what it means.<br><br>2. it is unnecessarily divisive. The people most likely to try out<br>Bazaar probably already have a favourite VCS, and may be turned off if
<br>their first exposure to Bazaar is a t-shirt saying how bad that VCS<br>is.<br><br>3. With great tools like bzr-svn, tailor and the Launchpad<br>vcs-imports, it isn't an exclusive situation: Bazaar can make you more
<br>productive when contributing to projects using a Subversion mainline.<br>They don't have to give up their current infrastructure to try Bazaar.<br><br>James.<br></blockquote></div><br><br clear="all"><br>-- <br><br>
<br><br>I code therefore I am.