Oh cool, another change to fig/docker-compose that doesn't include the most requested feature: https://github.com/doc...
Oh cool, another change to fig/docker-compose that doesn't include the most requested feature: https://github.com/docker/compose/issues/495 As the person who wrote the PR for its solution and have been waiting for it to get merged for months, this is super, super frustrating. If you guys don't want to put the logic in, reject the PR and close the issue as won't fix. Quit stringing the community along.
Posted by languagehacker on Apr 16, 2015, 11:37 PM
Tags
Related issues
- That isn't really relevant for the tool starting the container.
- Why is there no link to the source?
- Something I wonder about in this domain is if this is the fault of the language.
- Namespace pollution is an annoying problem in Rust.
- Currently, no language ports of Timefold Solver are planned.
- I agree with you, almost all .NET code I write is within the .NET framework, yet when I look at C# repos, it's disheartening to see so ma...
Raise real-world problems, find people facing the same issue, and discuss solutions.7,000 issues0 comments
hackernews (Software)
That isn't really relevant for the tool starting the container.
Why is there no link to the source?
Something I wonder about in this domain is if this is the fault of the language.
Namespace pollution is an annoying problem in Rust.
Currently, no language ports of Timefold Solver are planned.
I agree with you, almost all .NET code I write is within the .NET framework, yet when I look at C# repos, it's disheartening to see so ma...
Why is there no simple workaround for this?
I have been using https://github.com/jacktasia/dumb-jump to quickly jump to definitions.
Oh cool, another change to fig/docker-compose that doesn't include the most requested feature: https://github.com/doc...
Oh cool, another change to fig/docker-compose that doesn't include the most requested feature: https://github.com/docker/compose/issues/495 As the person who wrote the PR for its solution and have been waiting for it to get merged for months, this is super, super frustrating. If you guys don't want to put the logic in, reject the PR and close the issue as won't fix. Quit stringing the community along.
Comments (0)
No comments yet. Start the discussion.