unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Troy Figiel <troy@troyfigiel.com>
To: 68665@debbugs.gnu.org
Subject: [bug#68665] [PATCH 00/12 rust-team] gnu: Add Rust dependencies of python-cramjam.
Date: Tue, 23 Jan 2024 12:02:21 +0100	[thread overview]
Message-ID: <87msswgvnm.fsf@troyfigiel.com> (raw)
In-Reply-To: <877ck1hslb.fsf@troyfigiel.com>

[-- Attachment #1: Type: text/plain, Size: 711 bytes --]

Two short points:

1. It seems I forgot to add my copyright. In the past I added it to
crates-graphics.scm and not to crates-io.scm as I thought. I could add
an additional 13th patch, or maybe it would be easier to include it in
one of the other patches.

2. How is the cross-build-system depedency best handled? In the git logs
I have found two merges of the rust branch into master (1 month and 9
months ago), so if the merge happens once every ~6 months, it could be a
long wait. I am not in any rush, but in the meantime it does block me
from upstreaming other Python patches that depend on python-cramjam. If
there is a better way to handle this, I would love to know.

Best wishes,

Troy

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]

  parent reply	other threads:[~2024-01-23 11:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22 23:01 [bug#68665] [PATCH 00/12 rust-team] gnu: Add Rust dependencies of python-cramjam Troy Figiel
2024-01-22 21:34 ` [bug#68665] [PATCH 03/12] gnu: rust-lz4-1: Update to 1.24.0 Troy Figiel
2024-01-22 21:34 ` [bug#68665] [PATCH 01/12] gnu: rust-lz4-sys-1: Update to 1.9.4 Troy Figiel
2024-01-22 21:34 ` [bug#68665] [PATCH 02/12] gnu: rust-lz4-sys-1: Don't skip the build Troy Figiel
2024-01-22 21:45 ` [bug#68665] [PATCH 04/12] gnu: rust-lz4-1: " Troy Figiel
2024-01-22 21:54 ` [bug#68665] [PATCH 05/12] gnu: rust-cbindgen-0.24: Update to 0.24.5 Troy Figiel
2024-01-22 22:01 ` [bug#68665] [PATCH 06/12] gnu: Add rust-target-lexicon-0.11 Troy Figiel
2024-01-22 22:08 ` [bug#68665] [PATCH 07/12] gnu: Add rust-libdeflate-sys-1 Troy Figiel
2024-01-22 22:12 ` [bug#68665] [PATCH 08/12] gnu: rust-libdeflate-sys-0.11: Inherit from rust-libdeflate-sys-1 Troy Figiel
2024-01-22 22:20 ` [bug#68665] [PATCH 09/12] gnu: Add rust-libdeflater-1 Troy Figiel
2024-01-22 22:27 ` [bug#68665] [PATCH 10/12] gnu: rust-libdeflater-0.11: Inherit from rust-libdeflater-1 Troy Figiel
2024-01-22 22:46 ` [bug#68665] [PATCH 11/12] gnu: Add rust-inline-c-macro-0.1 Troy Figiel
2024-01-22 22:54 ` [bug#68665] [PATCH 12/12] gnu: Add rust-inline-c-0.1 Troy Figiel
2024-01-23 11:02 ` Troy Figiel [this message]
2024-01-23 14:36   ` bug#68665: [PATCH 00/12 rust-team] gnu: Add Rust dependencies of python-cramjam 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=87msswgvnm.fsf@troyfigiel.com \
    --to=troy@troyfigiel.com \
    --cc=68665@debbugs.gnu.org \
    /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).