From: jaeme via Guix-patches via <guix-patches@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: 66548@debbugs.gnu.org
Subject: [bug#66548] (no subject)
Date: Mon, 23 Oct 2023 01:38:56 -0400 [thread overview]
Message-ID: <81e5ec2a-65d1-4179-8c5c-65a07b34c2fb@runbox.com> (raw)
In-Reply-To: <8734y85ndm.fsf@cbaines.net>
I redid my patches again, I split it up into 2 patches for rust-alsa and
rust-alsa-sys since bitflags was updated on master.
On 10/18/23 04:44, Christopher Baines wrote:
> 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
next prev parent reply other threads:[~2023-10-23 5:40 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
2023-10-23 5:38 ` jaeme via Guix-patches via [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=81e5ec2a-65d1-4179-8c5c-65a07b34c2fb@runbox.com \
--to=guix-patches@gnu.org \
--cc=66548@debbugs.gnu.org \
--cc=jaeme@runbox.com \
--cc=mail@cbaines.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 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.