On Jun 8, 2009, at 11:19, Eric wrote:
> At 12:02 PM 6/8/2009, Tyler Roscoe wrote:
>> On Mon, Jun 08, 2009 at 06:35:59AM -0400, Eric wrote:
>>> Somebody else added a bunch of files to the repository. Shouldn't I
>>> be able to do an "Update" on the overall repository and get all
>>> new files? If that's not how it works, what is the accepted and
>> Yes, this is usually how it works. Is this not what you are seeing?
> That is not what I am seeing. The "update" (either from TSVN or from
> the command-line svn) does not see or download any of the new files.
> I had to blow away a whole directory out of my sandbox and then do an
> "update" in order to get two new files that someone else had put in
> that directory on the repository.
> There was another, whole new directory of files. I had to blow away
> the parent directory of that directory, in my sandbox, and then do an
> "update" to get them.
The reasons I can think of for this to occur are 1) your working copy
is corrupted in some way, or 2) you explicitly or your client
implicitly requested a sparse or nonrecursive checkout, whose purpose
is to behave as you describe and not pull in new items unless
explicitly requested. If you don't want that behavior, then you don't
use a sparse or nonrecursive checkout.
> Incidentally, when I blew away those directories and updated them in
> my sandbox, it totally screws up the file dating, i.e. it dates all
> the files with the current date and time. This is another issue
> that's unrelated to the problem I reported, but it causes real
> problems. This has been an issue since the early days of Subversion
> and has been reported and complained about many times by many people
> in many forums. I'm wondering (as an aside) if there are any plans
> to try to fix that at some point.
This is considered a feature, not a bug. When you check out or
update, modified and added files get their modification time set to
"now". This is what many software developers want, because it allows
the "make" program, which many software developers use, to know which
source files need to be recompiled.
If this is not what you want, perhaps because you don't use "make",
the other option available to you is to have added and modified files
get their modification time set to the commit time. You get this
behavior by setting "use-commit-times = yes" in your client's
Subversion config file.
Another option some people want is to have Subversion use the actual
modification time of the file, as distinct from the commit time. This
is not possible at present because Subversion does not store
modification times. The request to add this feature is filed here:
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-06-08 21:02:59 CEST