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

Re: Enhancement suggestion

From: Tom Mornini <tmornini_at_infomania.com>
Date: 2005-03-03 00:32:19 CET

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mar 2, 2005, at 3:08 PM, Brad O'Hearne wrote:

> So having the ability to have multiple contexts for a file within the
> same revision seems useful. Thoughts?

Two options, both of which should keep you considerably more sane than
your suggestion. :-)

1) Use branches for the different contexts, with regular (perhaps
automated?) merges from
    the trunk. Modify the files you wish to contextualize in the
branches.

2) extensions, sorted out during a build or installation routine. i.e.
file.conf.context1,
    and file.conf.context2, both independent and under version control.
Build (during packaging)
    or installation scripts determine proper context via user input or
environment, then
    rename the context file without the contextualized extension.

I'd use #1, though I've used #2 in the past. The nice thing about #1 is
that you can edit
the common files to make changes to the common parts that are not
contextually divergent
and the changes will automagically be made in the other branches on the
next merge.

- --
- -- Tom Mornini

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFCJk0EzaKkuvKwKvcRAjxZAJsF+Ym5/BFO9A2HvPD72GNiQYidJACdGJOB
Ow1pWod3ri1+mY9BzsHpFUY=
=lQQG
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 3 00:45:16 2005

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