| ▲ | cobbzilla 4 days ago | |
I see — you’re doing more than “here’s a few patches to keep working across revisions”, you’re doing separate-path feature work on a different, actively-developed project. To me that sounds like not a great idea, but if you must do it, I could see some usefulness to this. | ||
| ▲ | Nullabillity 4 days ago | parent [-] | |
Yeah. For reference, this is a typical patchset for the project that motivated it.[0] Some of the patches are "routine" dependency upgrades, some of them are bugfix backports, some of them are original work that we were planning to upstream but hadn't got around to yet. Some are worth keeping when upgrading to a new upstream version, some aren't. I agree that it's not ideal, but... there are always tradeoffs to manage. [0]: https://github.com/stackabletech/docker-images/tree/e30798ac... | ||