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

Re: feature request: append to last commit

From: Ben Collins-Sussman <sussman_at_red-bean.com>
Date: 2006-10-02 18:44:23 CEST

Unfortunately, this proposal goes against a fundamental design
principle of subversion -- tha revisions are immutable.

Suppose you commit revision 90, and then do a 'amendatory' commit to
revision 90 a couple of minutes later. But suppose somebody else did
an 'svn update' to r90 during that two-minute window. Now their
client has a different definition of r90 than somebody who runs 'svn
update' *after* the ammendatory commit. The former working copy is
going to get a big checksum error when the try to update to r91 later

If you're really worried about having the code always be in 'perfect'
state, then use branches. That's what they're for. Let the trunk be
unstable, and then port ranges of commits to a 'stable' branch
whenever the trunk is consistent. This guarantees that the branch
will *always* be stable.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 2 18:44:40 2006

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.