patches and low-level development discussion
 help / color / mirror / code / Atom feed
From: Alyssa Ross <alyssa.ross@unikie.com>
To: sternenseemann <sternenseemann@systemli.org>
Cc: devel@spectrum-os.org, Ville Ilvonen <ville.ilvonen@unikie.com>
Subject: Re: [RFC PATCH nixpkgs 8/9] ocamlPackages.wayland: 1.0 -> unstable-2022-05-07
Date: Wed, 28 Sep 2022 17:17:45 +0000	[thread overview]
Message-ID: <87pmffquyu.fsf@alyssa.is> (raw)
In-Reply-To: <42db4e87-aeaf-400e-a474-100db0774eeb@systemli.org>

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

sternenseemann <sternenseemann@systemli.org> writes:

> On 9/28/22 19:01, Alyssa Ross wrote:
>  > I've opened an issue[1] to ask for a new tag.
>
> Said release has been [published] just now. I think we can just update 
> this in upstream nixpkgs then (unstable version would've been fine, too, 
> honestly), unless updating nixpkgs is too big a trouble for you atm.
>
> [published]: https://github.com/talex5/ocaml-wayland/releases/tag/v1.1

Ah, fantastic.  Let's get it into upstream Nixpkgs as soon as we can
then.  I'll try to do it tomorrow if nobody has beaten me to it.

I don't know if I'll update Spectrum's Nixpkgs right away, but even if I
don't, cherry-picking a commit from upstream is still way better than
introducing a totally new commit to Spectrum's Nixpkgs.

(How did you notice the release so quickly, btw?  I'm impressed. :P)

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

  reply	other threads:[~2022-09-28 17:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-28 17:01 [RFC PATCH nixpkgs 0/9] virtio-gpu with crosvm and cloud-hypervisor Alyssa Ross
2022-09-28 17:01 ` [RFC PATCH nixpkgs 1/9] crosvm: switch back to old git repo URL Alyssa Ross
2022-09-28 17:01 ` [RFC PATCH nixpkgs 2/9] crosvm.updateScript: update release branch format Alyssa Ross
2022-09-28 17:01 ` [RFC PATCH nixpkgs 3/9] crosvm: 104.0 -> 106.2 Alyssa Ross
2022-09-28 17:01 ` [RFC PATCH nixpkgs 4/9] crosvm.updateScript: don't vendor Cargo.lock Alyssa Ross
2022-09-28 17:01 ` [RFC PATCH nixpkgs 5/9] crosvm: add fixes for cloud-hypervisor virtio-gpu Alyssa Ross
2022-09-28 17:01 ` [RFC PATCH nixpkgs 6/9] rustPlatform: forward unpack hooks to cargo fetch Alyssa Ross
2022-09-28 17:01 ` [RFC PATCH nixpkgs 7/9] cloud-hypervisor: add virtio-gpu support Alyssa Ross
2022-09-29  8:53   ` Alyssa Ross
2022-09-28 17:01 ` [RFC PATCH nixpkgs 8/9] ocamlPackages.wayland: 1.0 -> unstable-2022-05-07 Alyssa Ross
2022-09-28 17:09   ` sternenseemann
2022-09-28 17:17     ` Alyssa Ross [this message]
2022-09-29 12:35       ` sternenseemann
2022-09-28 17:01 ` [RFC PATCH nixpkgs 9/9] wayland-proxy-virtwl: unstable-2021-12-05 -> unstable-2022-08-06 Alyssa Ross

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=87pmffquyu.fsf@alyssa.is \
    --to=alyssa.ross@unikie.com \
    --cc=devel@spectrum-os.org \
    --cc=sternenseemann@systemli.org \
    --cc=ville.ilvonen@unikie.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://spectrum-os.org/git/crosvm
	https://spectrum-os.org/git/doc
	https://spectrum-os.org/git/mktuntap
	https://spectrum-os.org/git/nixpkgs
	https://spectrum-os.org/git/spectrum
	https://spectrum-os.org/git/ucspi-vsock
	https://spectrum-os.org/git/www

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 NNTP newsgroup(s).