From: Leo Famulari <leo@famulari.name>
To: Alexandros Theodotou <alex@zrythm.org>
Cc: 40468@debbugs.gnu.org
Subject: [bug#40468] [PATCH 3/3] gnu: Add shiru-lv2.
Date: Tue, 7 Apr 2020 16:08:55 -0400 [thread overview]
Message-ID: <20200407200855.GA15764@jasmine.lan> (raw)
In-Reply-To: <1fe07e3677e852cd9d502b68e4659879fc21e6b0.camel@zrythm.org>
On Tue, Apr 07, 2020 at 09:04:40PM +0100, Alexandros Theodotou wrote:
> > > > Does it work to inherit the custom install phase from dragonfly-
> > > > reverb?
> > > > It seems like the install-file procedures would not apply here.
> >
> > However, I tried building it from the patch and the install phase
> > does
> > fail there.
>
> Did you build it after applying the previous 2 patches?
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=40466 and
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=40467
>
> This is supposed to be merged after those changes. The first patch
> (40466) changes the install procedure in dragonfly-reverb, which is
> inherited here.
Ah, no, I didn't realize they were related.
It's annoyingly tricky, but patches that depend on each should be in the
same bug ticket. This can be accomplished by first sending an intro
message to get a bug number, then sending the patch series to e.g.
<NNN@debbugs.gnu.org>.
I'll merge them now.
next prev parent reply other threads:[~2020-04-07 20:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 14:16 [bug#40468] [PATCH 3/3] gnu: Add shiru-lv2 Alexandros Theodotou
2020-04-06 21:28 ` Alexandros Theodotou
2020-04-07 18:25 ` Leo Famulari
2020-04-07 19:09 ` Alexandros Theodotou
2020-04-07 19:41 ` Leo Famulari
2020-04-07 20:04 ` Alexandros Theodotou
2020-04-07 20:08 ` Leo Famulari [this message]
2020-04-07 20:14 ` Alexandros Theodotou
2020-04-08 15:41 ` Leo Famulari
2020-04-08 15:58 ` Alexandros Theodotou
2020-04-08 16:34 ` Alexandros Theodotou
2020-05-29 1:41 ` bug#40468: " Leo Famulari
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=20200407200855.GA15764@jasmine.lan \
--to=leo@famulari.name \
--cc=40468@debbugs.gnu.org \
--cc=alex@zrythm.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.