unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Martin Becze <mjbecze@riseup.net>
To: Leo Famulari <leo@famulari.name>,
	Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: rav1e AV1 encoder
Date: Fri, 28 Feb 2020 12:04:42 -0500	[thread overview]
Message-ID: <2f46b38d-97c8-71a3-d9aa-f47e32902678@riseup.net> (raw)
In-Reply-To: <20200227172613.GB30619@jasmine.lan>



On 2/27/20 12:26 PM, 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.
> 
> 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?
> 

Yeah I have also wondered this. I think it would make things a lot 
easier if we could do single commits.

  parent reply	other threads:[~2020-02-28 17:04 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
2020-02-28 17:04             ` Martin Becze [this message]
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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2f46b38d-97c8-71a3-d9aa-f47e32902678@riseup.net \
    --to=mjbecze@riseup.net \
    --cc=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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).