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

Re: ongoing problem with commites

From: Erik Huelsmann <ehuels_at_gmail.com>
Date: 2006-11-22 16:09:41 CET

On 11/22/06, Mark Nelson <markn@ieee.org> wrote:
> On 11/22/06, Erik Huelsmann <ehuels@gmail.com> wrote:
> >
> >
> > You need to have the latest and greatest in your working copy in order
> > for the files to end up in your repository. You probably didn't have
> > an up to date working copy when you started the commit, or someone
> > else checked in changes in the mean time.
>
> No, as I said in my post, that's not the problem.
>
> 1) Nobody else is using the repository, just me - and just from one location.
> 2) I can do an svn up, and I don't get anything new - I have the latest version.

That's not the same thing: doing 'svn up' and getting nothing new may
look like you have the latest and greatest, but in fact you don't:
Directories are regenerated for every commit. If you want to add a
file, you need to have the latest version of your directories, even if
there is no new content.

After the following series the containing directory 'dir' is still at
r1 and not at the latest version (see the Subversion book 'Mixed
revisions')

svn checkout http://host/repos rep-root
--> checked out r0
cd rep-root
echo 'foo' >file
svn add file
svn ci -m "Add file"
--> Revision 1

Then run:
svn info .
--> Revision: 0
svn info file
--> Revision: 1
svn update
svn info .
--> Revision: 1

Hope that helps.

bye,

Erik.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 22 16:11:04 2006

This is an archived mail posted to the Subversion Users mailing list.