If we are talking about non-developers things will get harder. But I have successfully merged Word documents with TortoiseSVN: it has a feature to open Word via Windows Scripting Host with the two documents that need merging.

The only problem there is that Word is/makes a mess: you will get all these supposed changes that are just field updates. And of course hardly anyone who uses Word knows how to do it properly (since those who do avoid it ;-) ). But these problems exist in the context of sending emails back and forth, too -- plus a lot of other ones, such as changes getting entirely lost due to concurrent updates and resulting overwrites.

But if you aim at a non-dev crowd I'd seriously look for alternatives.

  Peter



On 24/04/10 23:43, Edward Gabriel Moraru wrote:
Be aware that the business people sometimes edit the same document, and SVN/TortoiseSVN doesn't know how to merge binary files (as are treated doc, xls and ppt files)
Explain them how to use the "Get lock"/"Release lock" in TortoiseSVN.
It's a hard sell, I've tried and failed it, unfortunatedly.

Best of luck,
Edward.

On Sat, Apr 24, 2010 at 2:30 PM, Eric Jablow <[email protected] <mailto:[email protected]>> wrote:

    On Apr 23, 7:46 pm, Peter Becker <[email protected]
    <mailto:[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.

    Respectfully,
    Eric Jablow

    --
    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]
    <mailto:[email protected]>.
    To unsubscribe from this group, send email to
    [email protected]
    <mailto: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.

--
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.

Reply via email to