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

Re: cannot commit property data

From: Ben Collins-Sussman <sussman_at_red-bean.com>
Date: 2006-08-27 17:39:21 CEST

Seems like it would be a good idea to add a cross-reference to the
directory property limitation info in chapter 7. Thanks for the
suggestion.

It's hard to write a book which (a) reads straight through from start
to finish, logically building on itself, and (b) acts as a reference
manual, so that people can just open up to any point in the book and
get a full picture of what's going on. In some sense, those are
contradictory goals, so we're always in a constant state of
compromise.

On 8/27/06, Ralf Stephan <ralf@ark.in-berlin.de> wrote:
> You wrote
> > On 8/25/06, Ralf Stephan <ralf@ark.in-berlin.de> wrote:
> >
> > >Why should svn need to get some info back from the server it already
> > >has? I know I should always svn up before any commit but when you
> > >are the only committer you don't expect such an error.
> >
> > Please read chapter 2 in the svn book, 'basic concepts'. In
> > particular, see the section at the end about mixed revision working
> > copies. You cannot commit a propchange to a directory unless its
> > local revision is equal to HEAD. That's one of the only two
> > restrictions that exist:
>
> So, I didn't find it when I needed the info. I would have expected
> such information in the chapter about props, and I'm proposing to
> put it there, too. If these are the only exceptions, people won't
> complain about reading about them twice.
>
> > The error message, I hope, at least says *which* item is out of date.
> > Does it not?
>
> It does. So I studied the property chapter.
>
>
> Regards,
> ralf
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Aug 27 17:39:51 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.