all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: James Smith via Guix-patches via <guix-patches@gnu.org>
To: 73287@debbugs.gnu.org
Subject: [bug#73287] [PATCH 0/3] Add ericw-tools and TrenchBroom.
Date: Sun, 27 Oct 2024 07:30:19 -0700	[thread overview]
Message-ID: <86msipd3es.fsf@disroot.org> (raw)
In-Reply-To: <handler.73287.B.172645275019055.ack@debbugs.gnu.org> (GNU bug Tracking System's message of "Mon, 16 Sep 2024 02:13:02 +0000")

Hi,

I've waited about a month after sending a v2 and have gotten no
responses. Are there any more changes I need to make for a v3, or do I
just need to rebase onto current master?

Currently, the blocker I'm aware of is Embree 2 has a hard requirement
for SSE2. I'm thinking about mentioning it in the description when
sending v3, but I'd like to get a second opinion.

Thanks,

James




      parent reply	other threads:[~2024-10-27 14:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-16  2:10 [bug#73287] [PATCH 0/3] Add ericw-tools and TrenchBroom James Smith via Guix-patches via
2024-09-16  2:16 ` [bug#73287] [PATCH 1/3] gnu: Add embree-2 James Smith via Guix-patches via
2024-09-20  7:58   ` Liliana Marie Prikler
2024-09-21  0:35     ` James Smith via Guix-patches via
2024-09-16  2:16 ` [bug#73287] [PATCH 2/3] gnu: Add ericw-tools James Smith via Guix-patches via
2024-09-20  8:04   ` Liliana Marie Prikler
2024-09-16  2:16 ` [bug#73287] [PATCH 3/3] gnu: Add trenchbroom James Smith via Guix-patches via
2024-09-20  8:02   ` Liliana Marie Prikler
2024-09-21  0:38 ` [bug#73287] [PATCH v2 1/3] gnu: Add embree-2 James Smith via Guix-patches via
2024-09-21  0:38   ` [bug#73287] [PATCH v2 2/3] gnu: Add ericw-tools James Smith via Guix-patches via
2024-09-21  0:38   ` [bug#73287] [PATCH v2 3/3] gnu: Add trenchbroom James Smith via Guix-patches via
     [not found] ` <handler.73287.B.172645275019055.ack@debbugs.gnu.org>
2024-10-27 14:30   ` James Smith via Guix-patches via [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86msipd3es.fsf@disroot.org \
    --to=guix-patches@gnu.org \
    --cc=73287@debbugs.gnu.org \
    --cc=jsubuntuxp@disroot.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 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.