Process all matching rules - #123
Open
TWiStErRob wants to merge 1 commit into
Open
Conversation
Contributor
|
I'm really scared this will have unexpected side effects. A better solution would be to just run the conversion 3 times, once for each repo. |
Contributor
Author
|
I did that, @tnyblom, in the end. Would it make sense to detect this configuration and error on it? Because, at the moment, master is not failing and not producing the expected result either. |
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
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 have an SVN mono-repository, which has the following structure (unrelated stuff not listed):
and I would like to get three git repos for
project1andproject2andlibrary1. This is easy, except both those projects reference both libraries assvn:externalsonlibsfolders (^means relative to same SVN repo):there were many times when I committed to these projects and the libraries in the same commit.
I was thinking to set up rules like so:
and my expectation was that each shared commit will end up in every resulting repository so I would have a full history of the library by itself and the full history of the libs is also included in both projects.
This didn't work, so I hacked together the solution in this PR, which I wanted to share. It doesn't fully work, the resulting libs folders are not all equal, but much more usable for me than what
masterofsvn2gitproduces. Would it make sense to have this as a feature with a command line flag?For now I think I'll go with splitting my rules up and processing the source repo multiple times.