From: Efraim Flashner <efraim@flashner.co.il>
To: Sharlatan Hellseher <sharlatanus@gmail.com>
Cc: 63983@debbugs.gnu.org
Subject: [bug#63983] [PATCH] gnu: Add rust-heim-common-0.1.0.
Date: Wed, 7 Feb 2024 17:15:02 +0200 [thread overview]
Message-ID: <ZcOedlS7POvgzMyx@3900XT> (raw)
In-Reply-To: <CAO+9K5r+bV2zD=XX_LRjpO1FSw8pZhzw-UL4gi6E0iZdq63u3Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 812 bytes --]
On Mon, Feb 05, 2024 at 07:23:20PM +0000, Sharlatan Hellseher wrote:
> Hi Efrain,
>
> Which flow do you use for any new Rust packages e.g.
> merge to rust-team first or master would be ok?
I normally add them to the rust-team branch first since they often end
up needing to update some of the other packages already there.
It looks like this one slipped through the cracks during the summer.
I'm not exactly sure what to do with these patches, I'd adjust
rust-heim-common to accept any newer rust-mach-0.3, but rust-heim-common
by itself isn't a normal 'leaf package' that we'd add.
--
Efraim Flashner <efraim@flashner.co.il> רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-02-07 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 17:27 [bug#63983] [PATCH] gnu: Add rust-heim-common-0.1.0 Artyom V. Poptsov
2024-02-05 19:23 ` Sharlatan Hellseher
2024-02-07 15:15 ` Efraim Flashner [this message]
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=ZcOedlS7POvgzMyx@3900XT \
--to=efraim@flashner.co.il \
--cc=63983@debbugs.gnu.org \
--cc=sharlatanus@gmail.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).