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

Best practices question

From: Jonathan Wallace <jonathan.wallace_at_gmail.com>
Date: 2006-09-21 14:46:30 CEST

 I have a question concerning best practices. I have a set of files and
folders that make up a software program, let us call it program A, in
URL/trunk. The main "executable" is a microsoft .mdb file which must be
treated as binary and should only be edited by one person at any time as
merges are impossible[0] on binary files. There is also a program B that
shares a subset of the files in A including the main executable. For the
subset of files and folders shared between A and B, I'd like to insure that
there is only one copy of those files in the repository.

My first thought was to make B a branch of A but then if someone
accidentally commits the main executable in a checked out copy of B, then I
now have two copies. Obviously, one can merge this B executable back into
the main trunk but this doesn't solve the underlying problem. I appreciate
any and all suggestions.

0. If anyone knows that my assumption about merging source code in mdb files
is incorrect, I'd love to know.

Jonathan Wallace
Received on Thu Sep 21 14:47:08 2006

This is an archived mail posted to the Subversion Users mailing list.