Karl Auer <kauer@biplane.com.au> wrote on 02/13/2006 09:05:48 AM:
> On Mon, 2006-02-13 at 08:46 -0500, Mark Phippard wrote:
> > > - Project P is under version control
> > > - rename package "X.Y.Z" in project P to "X.Y.C.D"
> > > - commit the project "P"
> > > - Subversion (via Subclipse) complains that "X.Y.Z" is out of date.
> > >
> > > The workaround is to do Team->Update on Project P, then commit, but
IMHO
> > > this should not be necessary.
> >
> > This is a Subversion requirement. There is no way that Subclipse is
going
> > to fire off an update command without you telling us, so I do not see
what
> > else could be done here.
>
> I'm not understanding something; why is the update necessary at all? I'm
> committing, which to my way of thinking means more or less "this is how
> I want the directory to look; make it so". Maybe I just don't understand
> what exactly "out of date' means.
When you commit a folder change, the folder has to be at the HEAD
revision. Folders easily get behind the HEAD revision via Subversion's
concept of "mixed-revision" working copies. At it simplest, if commit
file foo, then file foo is updated to the HEAD revision as part of that
commit, but the folder that contains foo is not updated until you do an
explicit update.
http://subversion.tigris.org/faq.html#wc-out-of-date
http://svnbook.red-bean.com/en/1.0/ch02s03.html#svn-ch-2-sect-3.4
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Mon Feb 13 15:18:43 2006