Opened 18 years ago
Last modified 7 months ago
#3519 new enhancement
browse source - edit feature? — at Version 6
| Reported by: | anonymous | Owned by: | Christian Boos |
|---|---|---|---|
| Priority: | high | Milestone: | next-major-releases |
| Component: | version control | Version: | 0.9.6 |
| Severity: | normal | Keywords: | edit attachment patches |
| Cc: | itamarost@… | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description (last modified by )
It would be great if when browsing the source tree through the subversion repository, there was a way to pull up an "Edit" box to make quick edits to files and submit them to the subversion repository. This way I can give access to WIKI users to make edits to files within the subversion repository without them needing to set up full development environments.
Change History (6)
comment:1 by , 18 years ago
comment:2 by , 18 years ago
| Type: | defect → enhancement |
|---|
follow-up: 6 comment:3 by , 17 years ago
| Milestone: | → 2.0 |
|---|---|
| Owner: | changed from to |
Potentially useful for making small edits, like fixing typos, the inlined documentation, etc.
comment:6 by , 14 years ago
| Description: | modified (diff) |
|---|---|
| Keywords: | edit review zattachment patches added |
| Milestone: | triaging → next-major-0.1X |
| Priority: | normal → high |
Replying to cboos:
Potentially useful for making small edits, like fixing typos, the inlined documentation, etc.
And instead of "saving" by performing a commit, we could create a diff as an attachment to an existing ticket or to a new one (if the ticket field is left blank).
The "Review changes" page should present the diff in the usual way, but also a textarea containing the diff as plain text for copy/pasting (or should have a link to the raw diff).
That would be for the "Edit" feature, a related feature could be "Review" (a simple form of #2035), where the original text would be quoted (> ...), and the saving would create a new comment for the selected ticket (or, like in the above, a new ticket if the ticket field is left empty).
Those two features would be useful not only for source files in the repository, but also for attachments. Combined with a patch renderer that is more resilient to "fragmented" patches, it would make it easier to review patches.
Potential duplicates / related requests: #2956, #2755