From: Andrew Tropin <andrew@trop.in>
To: 45707@debbugs.gnu.org
Subject: [bug#45707] (no subject)
Date: Tue, 02 Feb 2021 23:00:02 +0300 [thread overview]
Message-ID: <8735yetf3x.fsf@trop.in> (raw)
In-Reply-To: <875z4963kf.fsf@gmail.com>
Hi everyone!
I have been doing the similar work related to obs load path and already
contibuted it to upstream [fn:1]. The patch was accepted and obs
currently support OBS_PLUGINS_PATH and OBS_PLUGINS_DATA_PATH out of the
box.
I've sent a patch with update to OBS version [fn:2] to get those changes
available in guix. Unluckily I was not aware of this thread before
Alexey replied to [fn:2] and also forgot to ask not to apply this patch.
As the changes [fn:1] is already in upstream and do the similar thing,
can we revert this patch and apply [fn:2] instead, please?
Sorry for missing this thread, forgetting to notify you earlier and all
the inconvenience.
* Footnotes
[fn:1] https://github.com/obsproject/obs-studio/pull/4067
[fn:2] http://issues.guix.gnu.org/46113
--
Best regards,
Andrew Tropin
next prev parent reply other threads:[~2021-02-02 20:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 23:36 [bug#45707] [PATCH] gnu: Add obs-v4l2sink Evan Straw
2021-01-06 23:42 ` Nicolò Balzarotti
2021-01-06 23:45 ` Evan Straw
2021-01-06 23:47 ` [bug#45707] [PATCH v2] " Evan Straw
2021-01-07 0:11 ` Nicolò Balzarotti
2021-01-07 4:37 ` Evan
2021-01-07 8:19 ` Alexey Abramov
2021-01-13 14:35 ` [bug#45707] [PATCH] " Ludovic Courtès
2021-01-15 16:47 ` Alexey Abramov
2021-01-16 21:47 ` Ludovic Courtès
2021-01-20 8:28 ` Alexey Abramov
2021-02-02 9:31 ` bug#45707: " Ludovic Courtès
2021-01-15 17:10 ` [bug#45707] [PATCH v2] " pelzflorian (Florian Pelz)
2021-01-15 19:25 ` Evan Straw
2021-02-02 20:00 ` Andrew Tropin [this message]
2021-02-03 14:40 ` [bug#45707] [PATCH] gnu: obs: Update obs to fb347c Andrew Tropin
2021-02-03 21:11 ` [bug#46113] " Ludovic Courtès
2021-02-04 10:45 ` guix-patches--- via
2021-02-04 12:49 ` bug#46113: " Andrew Tropin
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=8735yetf3x.fsf@trop.in \
--to=andrew@trop.in \
--cc=45707@debbugs.gnu.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 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).