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

Re: Feature request: Keyword $Rev$ with a twist

From: Josef Wolf <jw_at_raven.inka.de>
Date: 2002-08-01 10:24:47 CEST

On Thu, Aug 01, 2002 at 12:13:42AM +0200, Branko ??ibej wrote:

> >Having used CVS for about 10 years now, I still have no clue why you
> >all want those mixed-revs-stuff. Maybe someone could give me a good
> >use case?
> Oh my, that's a good one. CVS has mixed-revision working copies, too.

So your main argument is "We need mixed-revs because we always had

> When you "cvs commit", only your changes get sent to the server; your
> sandbox isn't updated to HEAD.
> As to use cases: When I say "svn ci", I don't want my working copy
> changed. If I want that, I say "svn up". It's as simple as that.

I don't agree with this one. Not modifying your working files on commit
is not related to mixed revs-stuff. When you already are at HEAD,
there is no reason to modify your working files, because they _already_
are up-to-date. Only the administrative area in the .svn directory
needs to be modified. When you are not at HEAD, the commit should
simply fail.

The use case you mentioned above arises only because you already
_have_ mixed revisions at the time of commit. In other words: the
current behavior on commit is needed because you were using mixed-revs
_before_ the commit. It is a _consequense_ of mixed-revs, but _not_ the
_reason_ to introduce mixed-revs in the first place.

There is no technical reason for the current behavior of cvs/svn, it
is a _political_ decision.

Maybe you could try again and give me a _real_ use case for mixed-revs?
Please do not mis-understand me: I _know_ there are real use cases for
mixed-revs. But I don't believe that those use-cases are so frequent
that it is worth to burden the day-by-day use.

But anyway, we already discussed this topic about two months ago and
agreed on leaving it as is for now and discuss it again after 1.0 is

-- Josef Wolf -- jw@raven.inka.de --
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 1 10:25:44 2002

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.