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

Re: confusing 'svn update'

From: Geoffrey <lists_at_serioustechnology.com>
Date: 2007-06-29 22:16:13 CEST

Eric Hanchrow wrote:
>>>>>> "Geoffrey" == Geoffrey <lists@serioustechnology.com> writes:
>
> Geoffrey> I execute an 'svn update' but my file remains unchanged.
> Geoffrey> Should it not be updated to reflect the recent changes
> Geoffrey> Billy Bob made?
>
> I would think so, assuming it's the "same" file (i.e., not some
> unrelated file, in a different directory, that happens to have the
> same name).
>
> Geoffrey> I then removed the file, run 'svn update' and the file
> Geoffrey> is replaced with the file that has Billy Bob's changes.
>
> Geoffrey> Someone have a ticket for the clue train for me?
>
> Yow, no. I'm as confused as you are. If you can come up with a
> precise set of steps that reliably reproduces the problem, I'd like to
> see it.

I'll see if I can reproduce the problem. Here are the exact steps:

1. Billy Bob modifies file on his laptop in his work area. Full path is
/foo/bar/foobar.pm. He is sitting in the /foo/bar directory. He
commits these changes.

2. I go to /foo/bar on my laptop. Execute 'svn update'. I do not get a
new version of foobar.pm. I remove my copy of foobar.pm. I execute
'svn update.' I get a new version of foobar.pm that contains the
changes Billy Bob put into the file.

This should be easily reproduced. I'll try to do that and post back my
results.

-- 
Until later, Geoffrey
Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
  - Benjamin Franklin
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 29 22:16:24 2007

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.