This repository has been archived by the owner on May 2, 2019. It is now read-only.
Cleanup in build scripts, hint for migration from svn #27
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.
Hello Scott,
I forked the progit-repository some weeks ago and made some minor changes in build scripts. Furthermore I added a notice in the migration process from svn which I missed when I converted our svn repositories. You can pull the changes from my repository fork.
I have a question about github processes: how can I keep my progit-repository-fork "rones/progit" up-to-date with the changes in the main repository "progit/progit"? I didn't find a button like "perform pull from origin" in the web interface. I also tried to add a remote to the "progit/progit" repository in my local installation, but I have no permission to fetch from it. Can you give me a small hint how to pull "upstream" changes into my own repository?
Greetings from munich/germany,
Reinhard Holler