SVN: support svn:log revprop changes #84
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added rudimentary support for svn:log revprop changes to permit SCI to keep repositories current when you have developers that don't get commit messages right first time. Doesn't deal with reopening "accidentally" closed issues.
|
@pantsmanuk I've been going through the backlog... I know it's been over 2 years, sorry about that. This PR does not apply cleanly, and TBH not being an SVN user myself, I'm not sure what to make of it. If this is still an issue worth implementing, may I ask you to rebase your feature branch to update the pull request ? Thanks. |
|
Without feedback from you, I'll close this PR. Feel free to reopen it with a rebase of the code or submit a new one. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've added rudimentary support for svn:log revprop changes to permit SCI to keep repositories current when you have developers that don't get commit messages right first time. Doesn't deal with reopening "accidentally" closed issues, if you guys can figure that one out you'll be Gods in my eyes.