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

Re: Re: Questions about using subversion for non-coding projects.

From: Darren L <xlr8me_at_gmail.com>
Date: 2005-08-25 23:43:21 CEST

Hey,

This was a topic that came up recently, and I recommended the same
thing for a coworker - the TortoiseSVN plugin works amazingly well,
but the only complaint was that locking a file does not show up
immediately in other people's repositories (I believe that this was by
design, as it's built for offline use). The problem was that locking
a binary file left the possibility of two users working on the same
file without knowledge that theother was making changes.

Although this would show up when they attempted to check in the files,
it isn't possible to merge in changes in other formats of files.

Did I misunderstand this?
-Darren

On 8/25/05, Young, Jason (GE Infrastructure) <Jason.Young@ge.com> wrote:
> Actually, I thought that too and put locking on some word documents. I
> found out that Word has some kind of built-in merging (or so I was
> told). Subversion also handles the revisions just fine, and does not
> take up a lot of space for each change. I made a change to a 400kb word
> doc, and it only added 2kb to the repo size.
>
> -----Original Message-----
> From: Toby Johnson [mailto:toby@etjohnson.us]
> Sent: Thursday, August 25, 2005 2:28 PM
> To: Jay Paulson
> Cc: users@subversion.tigris.org
> Subject: Re: Questions about using subversion for non-coding projects.
>
> Jay Paulson wrote:
>
> > The company I currently work for has many different projects, however
> > they are not coding projects. The projects are mainly research ones
> > with many documents (Word, Excell, PDF docs etc) that are used with
> > this research (mainly documents things about the research but usually
> > go through many versions before a final version is released).
>
> Subversion can handle any type of file. It is most commonly used with
> source files and other line-based files but it handles "binary" files
> such as Office docs just fine. For these office files, you will most
> likely be interested in using the locking features introduced in version
> 1.2, since these files are considered "unmergeable", that is, two people
> can't generally merge independent changes back to a single
> version-controlled document.
>
> However, the TortoiseSVN project (http://tortoisesvn.tigris.org/), which
> makes an excellent Windows Explorer plugin for Subversion, also now has
> scripts which allow merging of Word documents, although I've never
> actually used them. I don't believe there are any good, web-based tools
> which allow the full range of Subversion actions -- checkout, modify,
> etc. -- so you'd want something like TortoiseSVN for everyday actions
> anyway.
>
> > What is needed is some sort of version control system that team
> > members can use to share files, collaborate ideas, and basically have
> > a project tracker kind of like SourceForge.net.
>
> Subversion is only the version-control part of this; it has no project
> tracking or collaboration tools. However, Trac
> (http://www.edgewall.com/trac/) uses Subversion for its version control
> and also incorporates all these features. It's written in Python.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 25 23:45:10 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.