From: Jacob Hrbek <kreyren@rixotstudio.cz>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 57809@debbugs.gnu.org
Subject: [bug#57809] [PATCH] gnome-boxes: Patch 'qemu-img' path
Date: Sun, 18 Sep 2022 21:32:29 +0000 [thread overview]
Message-ID: <P5DFIR.K7JI549PMIPU2@rixotstudio.cz> (raw)
In-Reply-To: <8c563d18-53eb-49ef-467f-29c3d242fea6@telenet.be>
[-- Attachment #1.1.1: Type: text/plain, Size: 1058 bytes --]
On Ne, zář 18 2022 at 23:14:12 +0200, Maxime Devos
<maximedevos@telenet.be> wrote:
> I find (search-input-file inputs "/bin/qemu-img") clearer -- 'inputs'
> /
> 'native-inputs' is sufficiently complicated on its own, no need to
> bring
> %build-inputs and friends in the equation when it can be avoided.
That ain't working for me: <https://i.imgur.com/Co4Xsjl.png>
unbound-variable #f "Unbound variable: ~S" (native-inputs) #f
> (1) the convention is TODO or FIXME, not NOTE
It's not:
- TODO as in "To Do something" or "for something to be done"
- FIXME as in "Low priority thing or quality assurance something that
needs to be fixed"
More like handing over note to the next guy about possible issue in the
future and leaving the signature here so that they can just go on chat
and ask instead of wasting ~3 min on average searching git blame/log
which gets exponentially more unsustainable to track
At least that's how it works where i work O_o .. personally i find it
better way than the generic TODO/FIXME
[-- Attachment #1.1.2: Type: text/html, Size: 1462 bytes --]
[-- Attachment #1.2: publickey - kreyren@rixotstudio.cz - 1677db82.asc --]
[-- Type: application/pgp-keys, Size: 713 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]
next prev parent reply other threads:[~2022-09-18 21:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 18:17 [bug#57809] [PATCH] gnome-boxes: Add 'qemu' as propagated-input Jacob Hrbek
2022-09-14 18:18 ` [bug#57810] " Jacob Hrbek
2022-09-15 13:03 ` [bug#57809] " Maxime Devos
2022-09-18 20:43 ` [bug#57809] [PATCH] gnome-boxes: Patch 'qemu-img' path Jacob Hrbek
2022-09-18 21:05 ` Jacob Hrbek
2022-09-18 21:14 ` Maxime Devos
2022-09-18 21:32 ` Jacob Hrbek [this message]
2022-09-18 21:50 ` Maxime Devos
2022-09-19 4:28 ` Jacob Hrbek
2022-09-19 13:35 ` Maxime Devos
2022-09-18 20:46 ` Jacob Hrbek
2022-09-18 20:47 ` [bug#57809] [PATCH] gnome-boxes: Add 'qemu' as propagated-input Jacob Hrbek
2022-09-19 4:09 ` [bug#57809] [PATCH] gnome-boxes: Patch 'qemu-img' path Jacob Hrbek
2022-09-19 13:41 ` Maxime Devos
2022-09-26 21:03 ` bug#57809: [PATCH] gnome-boxes: Add 'qemu' as propagated-input Ludovic Courtès
2022-09-19 21:36 ` [bug#57809] [PATCH] gnome-boxes: Fix path for 'qemu-img' Jacob Hrbek
2022-09-20 5:18 ` Liliana Marie Prikler
2022-09-20 7:55 ` Jacob Hrbek
2022-09-20 17:12 ` Liliana Marie Prikler
2022-09-26 21:07 ` [bug#57809] [PATCH] gnome-boxes: Add 'qemu' as propagated-input Ludovic Courtès
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=P5DFIR.K7JI549PMIPU2@rixotstudio.cz \
--to=kreyren@rixotstudio.cz \
--cc=57809@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
/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.