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

RE: .svn folder needs to stay

From: Madan U Sreenivasan <madan_at_collab.net>
Date: 2005-09-06 09:49:13 CEST

On Tue, 2005-09-06 at 12:59, Leon Zandman wrote:
> > This might work out in a software dev case... but not in
> > cases described above. How can a technical person decide
> > whether a work of art ( or whatever artifact the end user has
> > created) is worthy of checking in, unless he is a man of the
> > trade himself?!
> What made you think the technical person has to decide anything?
+ On Mon, 2005-09-05 at 12:16, Leon Zandman wrote:
+ [snip]
+ I have to submit my changes (patches) to one
+ of the repository maintainers who will then decide if they commit it.
   Thats why!!

> When an
> artist feels his work is ready for a commit (this might be the case at
> the end of each working day) he contacts the repository maintainer, who
> will then have to commit the work, possibly even without looking at it.

> This isn't about adding an extra decision layer in the process, but it's
> about delegating the "very difficult" task of managing an SCM repository
> to someone who knows how to handle it.
Isn't auto-versioning better?


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 6 09:42:33 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.