From: Andreas Enge <andreas@enge.fr>
To: Lilah Tascheter <lilah@lunabee.space>
Cc: guix-devel@gnu.org
Subject: Re: weird mumi message dupe/drop?
Date: Mon, 30 Sep 2024 12:14:09 +0200 [thread overview]
Message-ID: <Zvp58dVC0uhNII55@jurong> (raw)
In-Reply-To: <dbe2b709383d578a8bf8b9a950451a08616299ce.camel@lunabee.space>
Hello Lilah,
Am Thu, Sep 26, 2024 at 11:59:03AM -0500 schrieb Lilah Tascheter:
> so, I just tried to apply v3 of issue #73202, but it failed, first
> trying to apply a regular email, then completely dropping the last
> patch (in email order, so actually patch 12/14). looking into it, it
> seems like the raw messages aren't indexed properly? when downloading
> the raw mbox for either @17 or @18, the message for @17 is returned.
> all subsequent messages are then shifted one earlier than they should
> be. so, mumi am just doesn't work at all.
> any clues wtf happened? honestly I'm not even sure where to report this
> (if to report this?) and if anyone can, like, fixup the patch series
> message files?
I suspect this is not a problem with Mumi, since
https://qa.guix.gnu.org/issue/73202
shows that the commits do not apply.
The QA page
https://qa.guix.gnu.org/patches
shows a number of patches that cannot be applied; the core-updates merge
probably has not made things easier.
It would be nice if submitters whose patches stopped applying could send
a new version of their commits.
Andreas
prev parent reply other threads:[~2024-09-30 10:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 16:59 weird mumi message dupe/drop? Lilah Tascheter
2024-09-30 10:14 ` 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
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=Zvp58dVC0uhNII55@jurong \
--to=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=lilah@lunabee.space \
/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).