Hello Michael and Sam,
and many thanks for the quick and detailed feedback and observations.
On 6/17/21 7:23 PM, Michael Lustfield wrote:
> From my perspective, you did a relatively adequate job documenting the oddity
> in
> d/copyright. It seems that this file rarely ever (never) changes, so dr
On Fri, 18 Jun 2021 12:53:37 +0200
"Diego M. Rodriguez" wrote:
> [...]
> Actually, while the upstream tarball (from PyPI) does not include the
> unicode.xml file, upon closer inspection upstream does include it in
> their GitHub releases. If using the release for packaging is technically
> viable
On Fri, Jun 18, 2021 at 11:09 AM Diego M. Rodriguez wrote:
> Actually, while the upstream tarball (from PyPI) does not include the
> unicode.xml file, upon closer inspection upstream does include it in
> their GitHub releases. If using the release for packaging is technically
> viable (looks like
Bone Baboon writes:
> Sections
> * Rust trademark policy
> * Impact on free software projects
>
> # Rust trademark policy
The conversation about the Rust Trademark policy issue has been
happening on several mailing lists and in different IRC channels. I
decided to write a new summary that bringin
4 matches
Mail list logo
