From: Adrien 'neox' Bourmault <neox@gnu.org>
To: 73393@debbugs.gnu.org
Subject: [bug#73393] [PATCH 2/2] services: sane-service-type: create lock path for plustek backend
Date: Sun, 22 Sep 2024 10:55:55 +0200 [thread overview]
Message-ID: <069c91c965bfd1550ab927b63601e70e1b98d98e.camel@gnu.org> (raw)
In-Reply-To: <3ad4ed8a692d86a9bef0b2ea56921ae2bf882957.1726827449.git.neox@gnu.org>
Sorry for all that noise, that's my first time using Debbugs and I got
a little lost here, trying to obtain a clear merge...
next prev parent reply other threads:[~2024-09-22 8:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 19:03 [bug#73391] [PATCH 0/2] SANE: fix a locking bug for plustek backend neox
2024-09-20 19:03 ` [bug#73392] [PATCH 1/2] gnu: sane-backends-minimal: fix lock path " neox
[not found] ` <handler.73392.B.172685906722683.ack@debbugs.gnu.org>
2024-09-20 19:21 ` [bug#73392] Acknowledgement ([PATCH 1/2] gnu: sane-backends-minimal: fix lock path for plustek backend) Adrien 'neox' Bourmault
2024-09-20 19:03 ` [bug#73393] [PATCH 2/2] services: sane-service-type: create lock path for plustek backend neox
2024-09-22 8:55 ` Adrien 'neox' Bourmault [this message]
2024-09-20 20:39 ` [bug#73391] [PATCH v2 0/2] SANE: fix a locking bug " neox
2024-09-20 20:39 ` [bug#73391] [PATCH v2 1/2] gnu: sane-backends-minimal: fix lock path " neox
2024-09-21 8:03 ` [bug#73406] " Adrien 'neox' Bourmault
2024-09-22 9:07 ` [bug#73393] " Adrien 'neox' Bourmault
2024-09-20 20:39 ` [bug#73391] [PATCH v2 2/2] services: sane-service-type: create " neox
2024-09-21 8:03 ` [bug#73406] " Adrien 'neox' Bourmault
2024-09-22 9:07 ` [bug#73393] " Adrien 'neox' Bourmault
2024-09-21 8:01 ` [bug#73406] [PATCH v2 0/2] SANE: fix a locking bug " Adrien 'neox' Bourmault
2024-09-22 9:07 ` [bug#73393] " Adrien 'neox' Bourmault
2024-09-24 18:51 ` Liliana Marie Prikler
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=069c91c965bfd1550ab927b63601e70e1b98d98e.camel@gnu.org \
--to=neox@gnu.org \
--cc=73393@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).