I think TortoiseCVS is a pretty good choice. jitesh dundas
On Sun, Apr 25, 2010 at 5:02 AM, Peter Becker <[email protected]>wrote: > On 24/04/10 21:30, Eric Jablow wrote: > >> On Apr 23, 7:46 pm, Peter Becker<[email protected]> wrote: >> >> >>> But let's think more practical. Number one I would sell is the move from >>> CVS to SVN. CVS is just too scary due to it's lack of atomic commits. >>> The consistent revision number across the repository is another nice >>> feature in SVN. While I agree with other posters that there are >>> technically superior options, I wouldn't even propose them based on the >>> description of the organizational culture. SVN makes me swear sometimes, >>> but it is leagues better than CVS. Setting up an SVN/trac combo is >>> pretty straightforward, although it of course means someone has to deal >>> with security patches and backups. >>> >>> >> I would add TortoiseSVN to the list, as long as you stay with Windows. >> I'd even push it to the non-programmers. Budget memos and requirement >> documents need version control too. >> >> > Since they already use TortoiseCVS I assumed that to be implied :-) > > Peter > > > -- > You received this message because you are subscribed to the Google Groups > "The Java Posse" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<javaposse%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > > -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
