Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

time to retire pipes-platform? #11

Open
tonyday567 opened this issue Sep 8, 2013 · 3 comments
Open

time to retire pipes-platform? #11

tonyday567 opened this issue Sep 8, 2013 · 3 comments

Comments

@tonyday567
Copy link
Contributor

I just reread the git submodule man pages, whatever links I could find and came to the conclusion that:

  1. Git submodules are tragically flawed and downright evil
  2. There is no possible way to set things so that branches are automatically tracked and easily refreshed to the latest commits

At the moment, several of the submodule commits are behind the latest master HEADS. If I were to refresh them, they would be again be behind upon the next commit in any of the projects.

I think the easiest solution is to abandon the notion of pipes-platform, and wind down the notion of pipes-platform, perhaps starting again with pipes-examples ie a clean repo to place extended examples etc.

@Gabriella439
Copy link
Owner

Let me first finish up the remaining issues and then we can set up a pipes-platform repository.

@Gabriella439
Copy link
Owner

Oops, I meant pipes-examples, like you suggested.

@tonyday567
Copy link
Contributor Author

Yep, great!

tony day
tonyday567@gmail.com

On 8 Sep 2013, at 14:52, Gabriel Gonzalez notifications@github.com wrote:

Oops, I meant pipes-examples, like you suggested.


Reply to this email directly or view it on GitHub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants