From: Olivier Rojon <o.rojon@posteo.net>
To: 71196@debbugs.gnu.org
Cc: zimon.toutoune@gmail.com, paren@disroot.org, ludo@gnu.org,
me@tobias.gr, rekado@elephly.net, jgart@dismail.de,
othacehe@gnu.org, guix@cbaines.net
Subject: [bug#71196] Mentoring for Mixxx package update
Date: Thu, 30 May 2024 06:25:20 +0000 [thread overview]
Message-ID: <878qzrerzj.fsf@> (raw)
In-Reply-To: <20240525125955.27269-1-o.rojon@posteo.net>
Hello everyone
in case you are now notified twice (once with the patches and once with this
message), please agologize the noise. I am still learning the ins and outs of submitting
patches.
I am just writing here to make sure that mentors see the issue, because I'd love to see
these changes merged/included in Guix and get feedback on my (pretty messy IMO) process of
submitting the patch.
Have a good day and thanks for your time,
Olivier
next prev parent reply other threads:[~2024-05-30 7:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-25 12:59 [bug#71196] [PATCH 0/3] *** Update Mixxx and depdendencies *** hapster
2024-05-26 6:20 ` [bug#71196] [PATCH 1/3] gnu/packages/music: Update Mixxx to 2.4.1 hapster
2024-05-26 6:20 ` [bug#71196] [PATCH 2/3] gnu/packages/audio: Update Soundtouch to 2.3.1 hapster
2024-05-26 6:20 ` [bug#71196] [PATCH 3/3] gnu/packages/libusb: Update hidapi to 0.14.0 hapster
2024-05-26 6:42 ` [bug#71196] [PATCH 1/3] gnu/packages/music: Update Mixxx to 2.4.1 hapster
2024-05-26 6:42 ` [bug#71196] [PATCH 2/3] gnu/packages/audio: Update Soundtouch to 2.3.1 hapster
2024-05-26 6:42 ` [bug#71196] [PATCH 3/3] gnu/packages/libusb: Update hidapi to 0.14.0 hapster
2024-05-30 6:25 ` Olivier Rojon [this message]
2024-05-30 15:19 ` [bug#71196] Mentoring for Mixxx package update jgart via Guix-patches via
2024-06-03 19:52 ` Olivier Rojon
2024-06-03 21:49 ` jgart via Guix-patches via
2024-06-05 14:49 ` Olivier Rojon
2024-06-05 15:13 ` jgart via Guix-patches via
2024-06-09 8:46 ` Olivier Rojon
2024-06-30 10:41 ` bug#71196: Pushed Andreas Enge
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=878qzrerzj.fsf@ \
--to=o.rojon@posteo.net \
--cc=71196@debbugs.gnu.org \
--cc=guix@cbaines.net \
--cc=jgart@dismail.de \
--cc=ludo@gnu.org \
--cc=me@tobias.gr \
--cc=othacehe@gnu.org \
--cc=paren@disroot.org \
--cc=rekado@elephly.net \
--cc=zimon.toutoune@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).