#4619 closed defect (worksforme)
Files are not shown up at new location after 'svn move' !!!
Reported by: | samvel | Owned by: | Christian Boos |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | version control/browser | Version: | 0.10.2 |
Severity: | critical | Keywords: | svn |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
I am using Trac version 0.10.2 After I have moved files in SVN repository from one folder to another Trac didn't show up changes in Code Browser.
svn co <code>
checks out code from repository taking into account new locations of files.
Am I missing something or this is a bug?
Attachments (0)
Change History (6)
follow-up: 2 comment:1 by , 18 years ago
follow-up: 3 comment:2 by , 18 years ago
Replying to cboos:
That's probably a caching issue, which is why nobody should be using 0.10.2 anymore ;)
This is probably a duplicate of #4132, but I'll let you upgrade to 0.10.3 and report back if it works for you after that, before closing the ticket.
Thanks, let me try 0.10.3 first and I'll put results in here.
comment:3 by , 18 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Replying to anonymous:
Replying to cboos:
That's probably a caching issue, which is why nobody should be using 0.10.2 anymore ;)
This is probably a duplicate of #4132, but I'll let you upgrade to 0.10.3 and report back if it works for you after that, before closing the ticket.
Thanks, let me try 0.10.3 first and I'll put results in here.
Just have installed 0.10.3 The issue is resolved. Thanks for help.
comment:4 by , 18 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
comment:5 by , 18 years ago
Keywords: | move miss file removed |
---|---|
Priority: | highest → normal |
Resolution: | → worksforme |
Status: | reopened → closed |
comment:6 by , 18 years ago
(note that the trick here is that even a restart of your 0.10.2 installation would have fixed the issue… but with 0.10.3, it shouldn't happen again)
That's probably a caching issue, which is why nobody should be using 0.10.2 anymore ;)
This is probably a duplicate of #4132, but I'll let you upgrade to 0.10.3 and report back if it works for you after that, before closing the ticket.