[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: rav1e AV1 encoder
From: |
Leo Famulari |
Subject: |
Re: rav1e AV1 encoder |
Date: |
Thu, 27 Feb 2020 12:26:13 -0500 |
I'm wondering if I can just push the crates as a single commit, after
inserting them alphabetically and fixing any cosmetic issues, and also
handling the semver-compatible package updates.
I know that we don't usually do this when adding packages to an existing
module. We do add packages en masse when creating a new module.
The reason I'm asking to make an exception to our policy of one package
or update per commit are that it will be a ton of work (several full
days at least) to add software that is already working fine on the
wip-rav1e branch.
I don't see what value this additional labor will give to Guix users,
including developers. At least, I don't think the value of individual
commits will outweigh the value of my labor in this case.
What do you all think?
- Re: rav1e AV1 encoder, (continued)
Re: rav1e AV1 encoder, Leo Famulari, 2020/02/25
- Re: rav1e AV1 encoder, John Soo, 2020/02/25
- Re: rav1e AV1 encoder, Leo Famulari, 2020/02/25
- Re: rav1e AV1 encoder, Efraim Flashner, 2020/02/26
- Re: rav1e AV1 encoder, Leo Famulari, 2020/02/27
- Re: rav1e AV1 encoder, Efraim Flashner, 2020/02/28
Re: rav1e AV1 encoder,
Leo Famulari <=
Re: rav1e AV1 encoder, Efraim Flashner, 2020/02/28
Re: rav1e AV1 encoder, Martin Becze, 2020/02/28