From: Junio C Hamano <gitster@pobox.com>
To: "Elijah Newren via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Elijah Newren <newren@gmail.com>
Subject: Re: [PATCH] merge-ort: fix missing early return
Date: Sat, 06 Jul 2024 11:30:38 -0700 [thread overview]
Message-ID: <xmqqr0c6nzjl.fsf@gitster.g> (raw)
In-Reply-To: <pull.1758.git.1720123341342.gitgitgadget@gmail.com> (Elijah Newren via GitGitGadget's message of "Thu, 04 Jul 2024 20:02:21 +0000")
"Elijah Newren via GitGitGadget" <gitgitgadget@gmail.com> writes:
> From: Elijah Newren <newren@gmail.com>
>
> One of the conversions in 500433edf49 ("merge-ort: convert more error()
> cases to path_msg()", 2024-06-10) accidentally lost the early return.
f19b9165 (merge-ort: convert more error() cases to path_msg(),
2024-06-19) is what I have, date is different (and object name is,
too, obviously).
And funny thing is that your base-commit points at the latter. I
briefly wondered if we can somehow automate the generation of
reference in the log message, but the base is likely to be the tip
of the topic branch that has been accepted upstream, and the commit
being fixed up can be something below, not at, that tip, so it
wouldn't be like a simple and silly "compare base-commit and the
commit we talk about in the proposed log message".
A commit-msg hook that scans for names that look like commit object names in the
message, and
- makes sure that these commits are reachable from HEAD (the goal
is to make sure they are reachable from the resulting commit),
and possibly
- makes sure that these commits are reachable from @{u} (the goal
is to catch references of unpublished commits)
might be a possibility, but such criteria are probably highly
workflow specific, so needs to be highly customizable if we wanted
to make such a feature as a part of what we ship.
> Restore it.
>
> Signed-off-by: Elijah Newren <newren@gmail.com>
> ---
Thanks. I saw Peff's earlier message and the change exactly matches
my expectation. Will queue (with adjustments to the log message).
> merge-ort: fix missing early return
>
> This is a patch on top of en/ort-inner-merge-error-fix which is in next.
>
> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1758%2Fnewren%2Ffix-fix-error-cases-v1
> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1758/newren/fix-fix-error-cases-v1
> Pull-Request: https://github.com/gitgitgadget/git/pull/1758
>
> merge-ort.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/merge-ort.c b/merge-ort.c
> index 8dfe80f1009..d9ba6e3e523 100644
> --- a/merge-ort.c
> +++ b/merge-ort.c
> @@ -3618,6 +3618,7 @@ static int read_oid_strbuf(struct merge_options *opt,
> path_msg(opt, ERROR_OBJECT_NOT_A_BLOB, 0,
> path, NULL, NULL, NULL,
> _("error: object %s is not a blob"), oid_to_hex(oid));
> + return -1;
> }
> strbuf_attach(dst, buf, size, size + 1);
> return 0;
>
> base-commit: f19b9165351a4058832bb43560178474c7501925
next prev parent reply other threads:[~2024-07-06 18:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 20:02 [PATCH] merge-ort: fix missing early return Elijah Newren via GitGitGadget
2024-07-06 6:28 ` Jeff King
2024-07-06 18:30 ` Junio C Hamano [this message]
2024-07-07 2:50 ` Elijah Newren
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=xmqqr0c6nzjl.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=newren@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 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 NNTP newsgroup(s).