On Jan 27, 2006, at 23:29, Rob Brandt wrote:
>> Specifically the last paragraph.
> Yeah, I understand that in concept, just not why it applies here.
> Here's the
> full rundown on the steps I took:
> * Originally the /folder1/sub1/subsub1 folder was under source
> control. I
> realized this was a problem and read about the "ignore" attribute,
> that the attribute could be applied to any "unversioned" item.
> * Since it was already versioned and had nothing valuable in it, I
> used Tortoise
> to delete it.
> * I then committed the delete to the repository.
> * I then made a trivial change to one of the other files and
> committed it, to be
> sure that the system had "digested" the change and could go on.
> * I then used Explorer to create the folder again.
> * I then use Tortoise to "Add to Ignore list -> subsub1".
> * Then commit, and get the error I reported above.
> I should add that I am the only user here; version control is for
> me for
> mutliple locations, branches, tags, rollbacks, etc. Someone else
> could not
> have committed to the repository in the meantime.
> Since the only change was made to my working copy, it doesn't make
> sense to me
> that I would have to do an update first. But since it makes sense
> to you I
> must be missing something...
Every time you commit, your working copy gets into a mixed-revision
state. But Subversion requires that a directory be fully up-to-date
before it'll let you commit a property change. The trivial change you
made to an unrelated file was done in, say, revision 50. Then the
directory on which you're now trying to update the property is at a
revision less than 50, which is not the latest revision, which means
you must update it first before you can change a property on it.
In this case, since there were no changes in the repository for this
directory, ideally Subversion could have detected that the update
wouldn't do anything harmful, and done it automatically without
bothering you with a confusing error message. This has already been
filed as an enhancement request.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Jan 27 23:52:14 2006