From: Sergey Trofimov <sarg@sarg.org.ru>
To: 67534@debbugs.gnu.org
Cc: maxim.cournoyer@gmail.com
Subject: [bug#67534] Requesting review
Date: Thu, 21 Mar 2024 22:16:14 +0100 [thread overview]
Message-ID: <87le6b2s5b.fsf@sarg.org.ru> (raw)
In-Reply-To: <940c712802a6bb69dde97dca4b6c01524d0a0a1e.1701289507.git.sarg@sarg.org.ru>
Hi Maxim,
may I ask your review here, as you've authored qmk firmware
package. I'm adding `keyboard-source-directory` to the
`make-qmk-firmware` procedure, so that a custom firmware could be
built without upstreaming a keyboard definition to the main QMK
repo. Here is how I use it:
https://github.com/sarg/keyboard/blob/91b87a830ef6029c1023c0d8fc877c067b12ab1e/guix.scm
Best regards,
Sergey
next prev parent reply other threads:[~2024-03-21 21:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 20:32 [bug#67534] [PATCH] gnu: qmk: Support custom keyboards Sergey Trofimov
2024-03-21 21:16 ` Sergey Trofimov [this message]
2024-04-01 0:21 ` bug#67534: Requesting review Maxim Cournoyer
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=87le6b2s5b.fsf@sarg.org.ru \
--to=sarg@sarg.org.ru \
--cc=67534@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
/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).