From: Efraim Flashner <efraim@flashner.co.il>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: rav1e AV1 encoder
Date: Fri, 28 Feb 2020 15:30:43 +0200 [thread overview]
Message-ID: <20200228133043.GN12956@E5400> (raw)
In-Reply-To: <20200227172613.GB30619@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 1532 bytes --]
On Thu, Feb 27, 2020 at 12:26:13PM -0500, Leo Famulari wrote:
> 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.
>
It took me about 3 weeks to review ~270 patches for alacritty and it was
easily more than 20 hours.
> 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?
I suppose it's not that much different than updating all the GHC
packages in one go, except that they're more interconnected. I suppose
we could throw them all into the crates-io module and then hack on all
270 packages at once in a separate branch. That certainly would be easier
than adding them one at a time.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-02-28 13:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 22:43 rav1e AV1 encoder Leo Famulari
2020-02-21 9:15 ` Martin Becze
2020-02-21 16:16 ` Leo Famulari
2020-02-21 16:41 ` Leo Famulari
2020-02-21 16:43 ` Martin Becze
2020-02-21 16:46 ` Martin Becze
2020-02-21 16:56 ` Leo Famulari
2020-02-22 11:09 ` Martin Becze
2020-02-22 22:41 ` Leo Famulari
2020-02-24 11:02 ` Martin Becze
2020-02-25 20:08 ` Leo Famulari
2020-02-25 21:21 ` John Soo
2020-02-26 4:14 ` Leo Famulari
2020-02-26 7:09 ` Efraim Flashner
2020-02-27 17:16 ` Leo Famulari
2020-02-28 13:24 ` Efraim Flashner
2020-02-27 17:26 ` Leo Famulari
2020-02-28 13:30 ` Efraim Flashner [this message]
2020-02-28 17:04 ` Martin Becze
2020-04-02 22:31 ` sorting Rust crates [was Re: rav1e AV1 encoder] Leo Famulari
2020-04-12 15:22 ` Martin Becze
2020-04-14 20:08 ` Martin Becze
2020-04-26 17:05 ` rav1e AV1 encoder Efraim Flashner
2020-04-26 17:47 ` Leo Famulari
2020-04-26 17:48 ` Leo Famulari
2020-04-26 17:53 ` Efraim Flashner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200228133043.GN12956@E5400 \
--to=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.