From: Dragan Simic <dsimic@manjaro.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2024, #03; Fri, 5)
Date: Sat, 06 Apr 2024 03:11:14 +0200 [thread overview]
Message-ID: <36f7e1b7122b0bdeb2e8b70f69abd331@manjaro.org> (raw)
In-Reply-To: <xmqqy19rtygr.fsf@gitster.g>
On 2024-04-05 21:13, Junio C Hamano wrote:
> * ds/send-email-per-message-block (2024-04-05) 2 commits
> - SQUASH??? switch to separator semantics
> - send-email: make it easy to discern the messages for each patch
>
> "git send-email" learned to separate its reports on each message it
> sends out with an extra blank line in between.
>
> Expecting a reroll.
> cf. <8d47bd687f2ad80bbc1e1c86ae337327@manjaro.org>
> source:
> <0e087ed992def0746f3d437253248904c2126464.1712262791.git.dsimic@manjaro.org>
Done, the v3 is on the mailing list. [1]
[1]
https://lore.kernel.org/git/e3212c0a4ad331685c68c13afcdbced20982ab32.1712364420.git.dsimic@manjaro.org/
> * ds/fetch-config-parse-microfix (2024-04-05) 1 commit
> - fetch: return when parsing submodule.recurse
>
> A config parser callback function fell through instead of returning
> after recognising and processing a variable, wasting cycles, which
> has been corrected.
>
> Will merge to 'next'.
> source: <pull.1709.git.1712285542303.gitgitgadget@gmail.com>
Isn't this an example of a prefix collision, i.e. "ds/" points
to two different contributors?
next prev parent reply other threads:[~2024-04-06 1:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 19:13 What's cooking in git.git (Apr 2024, #03; Fri, 5) Junio C Hamano
2024-04-05 20:06 ` Jeff King
2024-04-06 1:11 ` Dragan Simic [this message]
2024-04-06 5:03 ` Junio C Hamano
2024-04-06 8:37 ` Dragan Simic
2024-04-06 16:55 ` Junio C Hamano
2024-04-06 17:01 ` Dragan Simic
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=36f7e1b7122b0bdeb2e8b70f69abd331@manjaro.org \
--to=dsimic@manjaro.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 read-only IMAP folder(s) and NNTP newsgroup(s).