From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Jelle Licht <jlicht@fsfe.org>
Cc: 60576-done@debbugs.gnu.org
Subject: bug#60576: [PATCH] gnu: patman: Fix incomplete get-maintainer patch.
Date: Tue, 10 Jan 2023 11:48:32 -0500 [thread overview]
Message-ID: <87y1qajpy7.fsf_-_@gmail.com> (raw)
In-Reply-To: <878rifeu9n.fsf@fsfe.org> (Jelle Licht's message of "Fri, 06 Jan 2023 13:12:52 +0100")
Hello,
Jelle Licht <jlicht@fsfe.org> writes:
> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>
>> The full set of patches already merged into the U-Boot is included for
>> simplicity and avoiding mistakes like the previous one, where a conflicting
>> hunk got dropped, causing the following error when running patman:
>>
>> WARNING: Unknown setting get_maintainer_script
>>
>> * gnu/packages/bootloaders.scm (u-boot) [source]: Replace the
>> u-boot-patman-fix-help.patch, u-boot-patman-local-conf.patch and
>> u-boot-patman-get-maintainer.patch with u-boot-patman-guix-integration.patch.
>> * gnu/local.mk (dist_patch_DATA): Update patch registrations.
>> * gnu/packages/patches/u-boot-patman-fix-help.patch: Delete file.
>> * gnu/packages/patches/u-boot-patman-get-maintainer.patch: Likewise.
>> * gnu/packages/patches/u-boot-patman-local-conf.patch: Likewise.
>> * gnu/packages/patches/u-boot-patman-guix-integration.patch: New file.
>>
>> Reported-by: Jelle Licht <jlicht@fsfe.org>
>
> I don't know the first thing about U-Boot, nor am I a poweruser of patman, but I
> can confirm this fixes my issue.
Thanks for the feedback; applied.
Enjoy patman!
--
Thanks,
Maxim
prev parent reply other threads:[~2023-01-10 16:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 16:59 [bug#60576] [PATCH] gnu: patman: Fix incomplete get-maintainer patch Maxim Cournoyer
2023-01-06 12:12 ` Jelle Licht
2023-01-10 16:48 ` Maxim Cournoyer [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
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=87y1qajpy7.fsf_-_@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=60576-done@debbugs.gnu.org \
--cc=jlicht@fsfe.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).