From: Wilko Meyer <w@wmeyer.eu>
To: Leo Famulari <leo@famulari.name>
Cc: Wilko Meyer <w@wmeyer.eu>, 66923@debbugs.gnu.org
Subject: [bug#66923] [PATCH 1/2] gnu: linux-libre 6.5: Update to 6.5.10.
Date: Sat, 04 Nov 2023 10:20:46 +0100 [thread overview]
Message-ID: <87h6m1etkr.fsf@wmeyer.eu> (raw)
In-Reply-To: <ZUWIhXA3oq_BjriL@jasmine.lan>
Hi Leo,
Leo Famulari <leo@famulari.name> writes:
> I can't get them to apply. Do you know what commit of guix.git they
> apply to?
I prepared these patches on a branch where my 6.6. updates were already
present, which caused one of the two patches to not apply properly. I
prepared a second revision of those based off the upstream
kernel-updates branch; which means it should now work properly.
> You can use the '--base=auto' option of Git when creating patches or
> sending a patch series to automatically include that information.
I'll do this in future patches, thanks for mentioning it!
--
Kind regards,
Wilko Meyer
w@wmeyer.eu
next prev parent reply other threads:[~2023-11-04 9:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 21:56 [bug#66923] [PATCH 0/2] linux-libre kernel updates (2023-11-03) Wilko Meyer
2023-11-03 21:58 ` [bug#66923] [PATCH 1/2] gnu: linux-libre 6.5: Update to 6.5.10 Wilko Meyer
2023-11-03 21:58 ` [bug#66923] [PATCH 2/2] gnu: linux-libre 6.1: Update to 6.1.61 Wilko Meyer
2023-11-03 23:55 ` [bug#66923] [PATCH 1/2] gnu: linux-libre 6.5: Update to 6.5.10 Leo Famulari
2023-11-04 9:20 ` Wilko Meyer [this message]
2023-11-04 18:49 ` Leo Famulari
2023-11-05 15:34 ` Leo Famulari
2023-11-05 16:06 ` Leo Famulari
2023-11-06 0:06 ` bug#66923: " Leo Famulari
2023-11-04 9:36 ` [bug#66923] [PATCH v2 1/2] gnu: linux-libre 6.1: Update to 6.1.61 Wilko Meyer
2023-11-04 9:36 ` [bug#66923] [PATCH v2 2/2] gnu: linux-libre 6.5: Update to 6.5.10 Wilko Meyer
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=87h6m1etkr.fsf@wmeyer.eu \
--to=w@wmeyer.eu \
--cc=66923@debbugs.gnu.org \
--cc=leo@famulari.name \
/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).