From: Christopher Baines <mail@cbaines.net>
To: Jaeme Sifat <jaeme@runbox.com>
Cc: 66548@debbugs.gnu.org
Subject: [bug#66548] (no subject)
Date: Wed, 18 Oct 2023 09:44:25 +0100 [thread overview]
Message-ID: <8734y85ndm.fsf@cbaines.net> (raw)
In-Reply-To: <9909834b-348c-462c-b061-09b7e69ff251@runbox.com>
[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]
Jaeme Sifat via Guix-patches via <guix-patches@gnu.org> writes:
> I revised my patch to not include older versions of rust-alsa as they
> are not needed.
>
>
> From bb9a39beb92190d315284196ee63274e359fa657 Mon Sep 17 00:00:00 2001
> From: jaeme <jaeme@runbox.com>
> Date: Sat, 14 Oct 2023 22:54:54 -0400
> Subject: [PATCH] gnu: Add rust-alsa
>
> * gnu/packages/crates-io.scm (rust-alsa-0.8): New variable.
> * gnu/packages/crates-io.scm (rust-alsa-sys-0.3): New variable.
> * gnu/packages/crates-io.scm (rust-bitflags-2): Update to 2.4.0.
> * gnu/packages/crates-io.scm: Update copyright header.
Hi Jaeme,
Would you be able to split this up in to three commits/patches, with one
package added/updated per commit?
I did try to apply the patch, but wasn't able to. I think Git took issue
with the format of the email (and it seemed to have lots of non breaking
spaces in it as well). Could you use git send-email to send the patches,
or maybe generate patch files and send them one by one as attachments if
git send-email isn't possible for you?
Thanks,
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2023-10-18 8:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-14 19:26 [bug#66548] [PATCH] gnu: Add rust-alsa Jaeme Sifat via Guix-patches via
2023-10-15 3:03 ` [bug#66548] (no subject) Jaeme Sifat via Guix-patches via
2023-10-18 8:44 ` Christopher Baines [this message]
2023-10-23 5:38 ` jaeme via Guix-patches via
2023-10-23 14:10 ` [bug#66695] Mistaken Email jaeme via Guix-patches via
2023-10-25 0:47 ` [bug#66695] jbranso--- via Guix-patches via
2023-10-25 1:03 ` [bug#66695] jbranso--- via Guix-patches via
2023-10-25 1:42 ` [bug#66695] (no subject) jaeme via Guix-patches via
2023-10-25 1:52 ` [bug#66695] close 66695 jaeme via Guix-patches via
2023-10-23 5:41 ` [bug#66548] [PATCH 01/02] gnu: Add rust-alsa-sys jaeme via Guix-patches via
2023-10-23 5:42 ` [bug#66548] [PATCH 02/02] gnu: Add rust-alsa jaeme via Guix-patches via
2023-10-24 1:26 ` [bug#66548] [PATCH 01/02] gnu: Add rust-alsa-sys jaeme via Guix-patches via
2023-10-24 1:27 ` [bug#66548] [PATCH 02/02] gnu: Add rust-alsa jaeme via Guix-patches via
2023-10-25 17:24 ` [bug#66548] Revised Patch After ~rust-cpal~ Merge jaeme via Guix-patches via
2023-10-25 17:29 ` [bug#66548] Updated with copyright header jaeme via Guix-patches via
2023-10-28 23:14 ` [bug#66548] [PATCH vREVISION] gnu: Add rust-alsa-0.8 Jaeme Sifat via Guix-patches via
2023-11-05 10:31 ` bug#66548: " 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=8734y85ndm.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=66548@debbugs.gnu.org \
--cc=jaeme@runbox.com \
/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).