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

Re: svn commit: rev 7193 - branches/svn-push

From: <kfogel_at_collab.net>
Date: 2003-09-25 20:20:04 CEST

Ben Collins-Sussman <sussman@collab.net> writes:
> I asked Shlomi in IRC: "is it really important for unstable svn-push
> development to have multiple rollback points?" He replied: "I think
> I'd like to have more than one changeset between every commit to the
> trunk."

Everything that happens in the repository is visible to the all of us.
Yes, in theory one can "just ignore" a branch, set one's mailer to
never show those commit mails, log messages, etc. But in practice,
taking the steps to filter out these bit of reality is annoying and
cumbersome; people usually don't get around to doing it.

Experimental branches are usually for long-running, complex tasks
whose intermediate stages are likely to break the tree. It's hard to
understand why a 200 line C file needs a branch in the public
repository! And anyway, the whole point is to have exactly one
logical changeset per commit.

If we were BitKeeper or Arch, there would be an obvious technical
solution to this :-). However, as we're Subversion, I'd prefer
Shlomi's private development to take place privately, unless there's
some compelling (to all of us) reason for the branch.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 25 22:08:18 2003

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.