From: Max Gautier <mg@max.gautier.name>
To: git@vger.kernel.org
Cc: mg@max.gautier.name, liu.denton@gmail.com
Subject: Re: Detecting squash-merged branches (and question about git-diff-tree)
Date: Tue, 3 Dec 2024 17:18:27 +0100 [thread overview]
Message-ID: <Z08vUxoyK67LXZc3@framework> (raw)
In-Reply-To: <Z08N4AlQKiNi-IOI@framework>
Uh, btw, there is a typo in the script in the previous email, it should
actually be:
commit_by_patch_ids[${patch_id[0]}]=$ref
on line 20 (instead of $patch_id[0])
Not sure how I ended up sending the wrong version.
--
Max Gautier
prev parent reply other threads:[~2024-12-03 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 13:55 Detecting squash-merged branches (and question about git-diff-tree) Max Gautier
2024-12-03 15:30 ` Kristoffer Haugsbakk
2024-12-03 15:51 ` Max Gautier
2024-12-03 17:42 ` Kristoffer Haugsbakk
2024-12-03 16:18 ` Max Gautier [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=Z08vUxoyK67LXZc3@framework \
--to=mg@max.gautier.name \
--cc=git@vger.kernel.org \
--cc=liu.denton@gmail.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.
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.