all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Sarah Morgensen <iskarian@mgsn.dev>
To: Jack Hill <jackhill@jackhill.us>
Cc: 49539@debbugs.gnu.org
Subject: [bug#49539] [PATCH] gnu: Add nginx-rtmp-module.
Date: Sat, 24 Jul 2021 15:07:54 -0700	[thread overview]
Message-ID: <86sg03pdqd.fsf_-_@mgsn.dev> (raw)
In-Reply-To: <alpine.DEB.2.21.2107221649500.2109@marsh.hcoop.net> (Jack Hill's message of "Thu, 22 Jul 2021 16:53:32 -0400 (EDT)")

Hi,

Glad I could help. I forgot to mention also, the `begin` probably isn't
necessary (it's probably leftover from when it was a snippet somewhere),
but as you say that can be taken care of over time.

Jack Hill <jackhill@jackhill.us> writes:

[...]

> P.S. The same opportunities for improvement exists in some of our other nginx
> modules, from which I copied this phase. The next time we update those might be
> a good time to clean them up.

How common is this? Would it warrant an nginx-build-system, or perhaps
even a common idiom/general system for packages using multiple sources?
Or are the ways in which these packages uses secondary sources different
enough that unifying them would be difficult?

--
Sarah




      parent reply	other threads:[~2021-07-24 22:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-12 20:39 [bug#49539] [PATCH] gnu: Add nginx-rtmp-module Jack Hill
2021-07-12 20:52 ` Jonathan Brielmaier
2021-07-12 21:11   ` Jack Hill
2021-07-12 21:13     ` [bug#49539] [PATCH v2] " Jack Hill
2021-07-22  4:05       ` [bug#49539] [PATCH] " Sarah Morgensen
2021-07-22 20:53         ` Jack Hill
2021-07-22 20:55           ` [bug#49539] [PATCH v3] " Jack Hill
2021-07-29 19:48             ` bug#49539: [PATCH] " Ludovic Courtès
2021-07-24 22:07           ` Sarah Morgensen [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=86sg03pdqd.fsf_-_@mgsn.dev \
    --to=iskarian@mgsn.dev \
    --cc=49539@debbugs.gnu.org \
    --cc=jackhill@jackhill.us \
    /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.