From: Leo Famulari <leo@famulari.name>
To: Martin Becze <mjbecze@riseup.net>
Cc: guix-devel@gnu.org
Subject: Re: rav1e AV1 encoder
Date: Tue, 25 Feb 2020 15:08:23 -0500 [thread overview]
Message-ID: <20200225200823.GA31497@jasmine.lan> (raw)
In-Reply-To: <9e81d5d5-1f2a-3c6d-5f99-c001d1a03b7f@riseup.net>
On Fri, Feb 21, 2020 at 04:15:43AM -0500, Martin Becze wrote:
> On 2/20/20 5:43 PM, Leo Famulari wrote:
> > And if so, should it
> > be done as a single commit? Or one-by-one?
>
> One-by-one unfortunately
I've been working on this and I've committed about 3000 lines of these
packages by hand.
But, I have a concern with committing these packages one at a time
alphabetically.
Since the packages refer to each other, committing them individually
breaks the build until the entire commit series is complete. This will
break `git bisect` for 267 commits (the number of packages).
I think it would be better to add the new crates alphabetically in a
single commit.
next prev parent reply other threads:[~2020-02-25 20:08 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 [this message]
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
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=20200225200823.GA31497@jasmine.lan \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=mjbecze@riseup.net \
/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).