Nikita Pekin
Nikita Pekin
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.
Yeah, shallow clone should have a much smaller footprint. I checked the zip, and it does include the `.gitmodules` file so if you want to parse that and download them...
With string-based operations it might be difficult, but I think it's still doable with nom. I'd still like to at least give it a try.
Hey! Thanks for the PR. I'll take a look at it. Might I ask why the interest in this old repo? :)
👍 sounds good. I mostly use GitHub actions on my projects now so that would be a welcome change. If it helps, here are snippets from my Github Actions config...
So some libraries I think we can pull out: - lmtp (the entire ltmp server) - message (the RFC2822 message implementation)
@uiri on second thought, yeah, you're right. I don't think decoupling LMTP is really beneficial in this case.
@uiri for the MIME/RFC2822 message library, will it be a separate repo or a sub-crate in this project? Also, any more ideas for things to refactor?
We could also do something with Auth and User, perhaps move them to an authentication module, as they're inherently independent of the rest of the code?
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.