From: Junio C Hamano <gitster@pobox.com>
To: Teng Long <dyroneteng@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2023, #07; Tue, 27)
Date: Wed, 28 Jun 2023 09:24:42 -0700 [thread overview]
Message-ID: <xmqqjzvneer9.fsf@gitster.g> (raw)
In-Reply-To: <20230628095421.7249-1-tenglong.tl@alibaba-inc.com> (Teng Long's message of "Wed, 28 Jun 2023 17:54:21 +0800")
Teng Long <dyroneteng@gmail.com> writes:
> Junio C Hamano <gitster@pobox.com> writes:
>
>> * tl/notes-separator (2023-06-21) 7 commits
>> - notes: introduce "--no-separator" option
>> - notes.c: introduce "--[no-]stripspace" option
>> - notes.c: append separator instead of insert by pos
>> - notes.c: introduce '--separator=<paragraph-break>' option
>> - t3321: add test cases about the notes stripspace behavior
>> - notes.c: use designated initializers for clarity
>> - notes.c: cleanup 'strbuf_grow' call in 'append_edit'
>>
>> 'git notes append' was taught '--separator' to specify string to insert
>> between paragraphs.
>> source: <cover.1685174011.git.dyroneteng@gmail.com>
>
> There are no pending issues I think ;-)
>
> Please let me know if there are some obstables to merge.
Yes, please do (this is not a message to Teng, but to others) ;-)
Thanks.
next prev parent reply other threads:[~2023-06-28 16:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 22:11 What's cooking in git.git (Jun 2023, #07; Tue, 27) Junio C Hamano
2023-06-28 9:54 ` Teng Long
2023-06-28 16:24 ` Junio C Hamano [this message]
2023-06-28 19:29 ` cw/header-compat-util-shuffle (was Re: What's cooking in git.git (Jun 2023, #07; Tue, 27)) Glen Choo
2023-06-28 21:03 ` Junio C Hamano
2023-06-28 21:18 ` Glen Choo
2023-06-28 22:31 ` Junio C Hamano
2023-06-28 22:47 ` Junio C Hamano
2023-06-28 23:58 ` What's cooking in git.git (Jun 2023, #07; Tue, 27) Junio C Hamano
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=xmqqjzvneer9.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=dyroneteng@gmail.com \
--cc=git@vger.kernel.org \
/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).