#11965 closed defect (worksforme)
Diff between two equal folders
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | version control/changeset view | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
I have a repository with two folders with the exact same files. When I prepare a diff to compare the two folders, I get a list with all the files (common to the folders), apparently edited. When I view the diffs, every single page says "No files". The unified diff file is empty… Isn't this a bug? Why list the files as edited if the diff is empty, since they haven't suffered any changes?
Attachments (0)
Change History (6)
follow-up: 3 comment:1 by , 9 years ago
| Component: | general → version control/changeset view |
|---|---|
| Resolution: | → cantfix |
| Status: | new → closed |
comment:2 by , 9 years ago
| Resolution: | cantfix → worksforme |
|---|
comment:3 by , 9 years ago
Replying to jomae:
Works for me. Please read NewTicketGuidelines before submitting a new ticket. Also, please ask on the mailing list and/or post how to proceed.
Ok, thanks. But can you tell me please how to solve the problem? Is it related with trac config?
comment:4 by , 9 years ago
Are you using prepare diff view? The form in prepare diff view has from and to revisions. Instead of reloading the form, you should edit the revisions in the form and resubmit it after your commits.
If the issue is not solved, please post the following on the mailing list.
- The details of the issue
- How to reproduce
- System information of your About Trac view
comment:5 by , 9 years ago
In the meantime I figured out what was the problem. I was commiting the first folder, then the other one, in separate commits. If I commit everything in the same commit, I get the expected result. Thank you for your patience and help.
Works for me. Please read NewTicketGuidelines before submitting a new ticket. Also, please ask on the mailing list and/or post how to proceed.