From: Andreas Enge <andreas@enge.fr>
To: 71196-done@debbugs.gnu.org
Subject: bug#71196: Pushed
Date: Sun, 30 Jun 2024 12:41:34 +0200 [thread overview]
Message-ID: <ZoE2XmfvWxNLLa77@jurong> (raw)
In-Reply-To: <20240525125955.27269-1-o.rojon@posteo.net>
Hello Olivier,
congratulations to your first contribution to Guix!
In the meantime QA has processed the patches, built its dependent packages
and given the green light (I think the threshold has been increased from
300 to 600).
I prefer to add the commits in the reverse order (first the dependencies,
then the leaves). I have added copyright lines for you and adapted the
commit log messages to our conventions. Finally I saw that you had dropped
a few patches, which need to be removed also from the git repository and
deregistered in the list of patches.
Pushed, and I am closing this issue.
Thanks,
Andreas
prev parent reply other threads:[~2024-06-30 10:42 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 ` [bug#71196] Mentoring for Mixxx package update Olivier Rojon
2024-05-30 15:19 ` 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 ` Andreas Enge [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=ZoE2XmfvWxNLLa77@jurong \
--to=andreas@enge.fr \
--cc=71196-done@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 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.