Opened 20 years ago
Closed 20 years ago
#1428 closed enhancement (fixed)
revision logs should stop on svn cp/mv's selectivily
Reported by: | Owned by: | Christian Boos | |
---|---|---|---|
Priority: | high | Milestone: | 0.9 |
Component: | version control/log view | Version: | 0.8.1 |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
when watching at a revision log, I'd like sometimes *explicitely* to see changeset log messages from before the svn move or copy as well.
please add it, otherwise, seeking for it just hard to live with :(
Attachments (0)
Change History (6)
comment:1 by , 20 years ago
Summary: | revision logs should display beyond svn cp/mv's → revision logs should stop on svn cp/mv's selectivily |
---|
comment:2 by , 20 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
I was initially thinking about adding a stop-on-copy
checkbox
in the revision log module,
but your suggestion about highlighting is better, as there might be
multiple copy/move events in the history of the path being examined.
comment:3 by , 20 years ago
Milestone: | 0.8.2 → 0.9 |
---|
Not for 0.8.2, which is only for critical/trivial bug fixes.
comment:4 by , 20 years ago
This should be implemented in [1515]. I'll wait for some feedback before closing the ticket.
comment:6 by , 20 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
… and that patch was applied in [1540]. I think that this ticket is also related to #426, at least care should be taken while implementing #426 that the information about the copy history is still apparent:
e.g, with 4 entries per page:
Page1:
root / branches / A
Revision Log for the current path at revision 134 (page 1)
- mod 134
- mod 123
- mod 111
- . . copied from /trunk
- . . mod 110
Page2:
root / branches / A
Revision Log for the current path at revision 134 (page 2)
- . . copied from /trunk
- . . mod 109
- . . mod 108
- . . mod 107
- . . mod 106
okay, quite the opposite. I changed the subject/summary respectivily.
either support for highlighting copy'move events or just cut the log on request there.