discussion and development of piem
 help / color / mirror / code / Atom feed
From: Leo <git@relevant-information.com>
To: Kyle Meyer <kyle@kyleam.com>, Leo <git@relevant-information.com>
Cc: piem@inbox.kyleam.com
Subject: Re: piem-am with multiple attached patches squashes the commits
Date: Sun, 03 Nov 2024 21:30:22 +0100	[thread overview]
Message-ID: <874j4o9i1t.fsf@> (raw)
In-Reply-To: <87r07s45x9.fsf@kyleam.com>

Kyle Meyer <kyle@kyleam.com> writes:

> Thanks for the report, and sorry for the very delayed reply.
>

Thank you for replying!  When I dug up the email that triggered this I
I found some work that I hadn't finished. 😅

>
> Odd.  I'm not able to trigger that behavior on my end, so any additional
> info for reproducing would be helpful (though, if you're not hitting
> into this regularly, I realize these details may be lost to time at this
> point).

I found the email that prompted this report.  I tried running `piem-am`
on it again, and I could observe the same behaviour as described
earlier.  I also tried to reproduce it with a minimum viable example in
a new repo, but then the expected behaviour occurred.  I can't really
find any meaningful difference between the two so I'm giving up for now.
Maybe someone else will encounter this again in the future.  I haven't
run into this since (and had honestly forgotten that the problem existed).

Cheers,
Leo

      reply	other threads:[~2024-11-03 20:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-14 20:21 piem-am with multiple attached patches squashes the commits Leo
2024-11-03 16:51 ` Kyle Meyer
2024-11-03 20:30   ` Leo [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://git.kyleam.com/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874j4o9i1t.fsf@ \
    --to=git@relevant-information.com \
    --cc=kyle@kyleam.com \
    --cc=piem@inbox.kyleam.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.kyleam.com/piem/

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).