On Tue, Apr 06, 2010 at 10:31:56AM -0400, Bob Archer wrote:
> > On Tue, Apr 06, 2010 at 07:04:42AM +0200, Branko Čibej wrote:
> > > On 05.04.2010 17:06, Stefan Sperling wrote:
> > > > An idea we're playing with to mitigate this problem is having
> > designated
> > > > properties in the svn: namespace which allow users to tell svn what
> > their
> > > > branching/merging strategy is.
> > >
> > > (Thereby making things even more flexible, complex, and error-prone.)
> > > In the light of previous discussions
> > I'd like to read them. Can you provide pointers?
> > > this is a less than optimal way of
> > > making branching and merging easier for users. This is another feature
> > > that would probably only be used by perhaps 1% of all users ...
> > Do you mean "used" or "configured" (as in setting the props)?
> Have you guys considered rather than storing all this info in the
> config file rather than versioned properties. Especially since it is
> config info. Then provide a WC level config sorted in a separate files
> such as .svnconfig ? This has the advantage of being hidden away...
> but also has the advantage of being easily managed by users. The
> .svnconfig file could even be a way to have WC level config that would
> override the global config file that is currently stored outside of
> the WC in the users folder. It would also be easy for a user to copy
> this file from one project to another.
If you throw in server-side configuration (another feature on the
roadmap), I kind of like the idea.
However, note that using properties to carry information about paths
(which is what branches are in Subversion) has the advantage that
when the path changes, the property follows the change. Maintaining
this information in a separate file would require users (or svn) to
keep this file in sync with changes made to the tree structure.
Received on 2010-04-06 16:36:28 CEST