Documentation for making changes #4
Merged
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
nickelsen
force-pushed
the
git-submodule-documentation
branch
from
72c5934 to
3d33300
Compare
nickelsen
changed the title
|
Very reasonable. |
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.
Documentation about how to juggle the git-repos when developing in the different components.
I think we should let ggpyjobs track
upstreambranch ofsc2readerinstead of a specific commit, so people can pull down updates automatically.I'm also planning to remove the ggpyjobs component in the root of the stack, since it's perfectly possible to work directly in
/vagrant/esdb/vendor/ggpyjobson the stack.Let me know what you think.