From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: Fluxbox switch source
Date: Sun, 21 Aug 2022 21:06:00 +0200 [thread overview]
Message-ID: <20220821190600.Nmq9COz9MS3rhFiZWsmVeXurlvjEbWcuGheInTWSGMI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36863@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 801 bytes --]
There's a merged pull request on the void-packages repository
Fluxbox switch source
https://github.com/void-linux/void-packages/pull/36863
Description:
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, x86_64
#### Comments
Ran into issues with the sourceforge tar using pregenerated aclocal.m4/make files. Saw that github is getting commits here and there and the source has autogen.sh so I built from there.
There are a few file differences from the sourceforge tar. From what I can tell:
- a `defaults.cc` generated by a makefile?
- some `tests/` are in github that aren't in sourceforge
- already made languages files in sourceforge
- updated docs that aren't in sourceforge
prev parent reply other threads:[~2022-08-21 19:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 2:55 [PR PATCH] " zlice
2022-04-26 2:56 ` [PR PATCH] [Updated] " zlice
2022-04-26 15:37 ` [PR REVIEW] " classabbyamp
2022-04-26 15:37 ` classabbyamp
2022-04-26 15:41 ` [PR PATCH] [Updated] " zlice
2022-04-26 15:42 ` [PR REVIEW] " zlice
2022-04-26 15:47 ` classabbyamp
2022-07-01 5:49 ` classabbyamp
2022-07-01 11:57 ` [PR PATCH] [Updated] " zlice
2022-08-21 19:00 ` classabbyamp
2022-08-21 19:06 ` classabbyamp [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=20220821190600.Nmq9COz9MS3rhFiZWsmVeXurlvjEbWcuGheInTWSGMI@z \
--to=classabbyamp@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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).