All of lore.kernel.org
 help / color / mirror / Atom feed
From: Teng Long <dyroneteng@gmail.com>
To: gitster@pobox.com
Cc: git@vger.kernel.org, sunshine@sunshineco.com
Subject: Re: What's cooking in git.git (Jan 2023, #03; Mon, 9)
Date: Thu, 12 Jan 2023 10:51:37 +0800	[thread overview]
Message-ID: <20230112025137.4286-1-tenglong.tl@alibaba-inc.com> (raw)
In-Reply-To: <xmqqlembu551.fsf@gitster.g>

Junio C Hamano <gitster@pobox.com> writes:

> * tl/notes--blankline (2022-11-09) 5 commits
>  - notes.c: introduce "--no-blank-line" option
>  - notes.c: provide tips when target and append note are both empty
>  - notes.c: drop unreachable code in 'append_edit()'
>  - notes.c: cleanup for "designated init" and "char ptr init"
>  - notes.c: cleanup 'strbuf_grow' call in 'append_edit'
> 
>  'git notes append' was taught '--[no-]blank-line' to conditionally
>  add a LF between a new and existing note.
> 
>  Expecting a reroll.
>  cf. <CAPig+cRcezSp4Rqt1Y9bD-FT6+7b0g9qHfbGRx65AOnw2FQXKg@mail.gmail.com>
>  source: <cover.1667980450.git.dyroneteng@gmail.com>

Sorry for late reply, I just post a new patch on this topic.

Thanks.

      parent reply	other threads:[~2023-01-12  2:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-09 14:58 What's cooking in git.git (Jan 2023, #03; Mon, 9) Junio C Hamano
2023-01-09 19:56 ` es/hooks-and-local-env (was "What's cooking in git.git (Jan 2023, #03; Mon, 9)") Eric Sunshine
2023-01-10 22:44 ` pb/doc-orig-head (was: Re: What's cooking in git.git (Jan 2023, #03; Mon, 9)) Philippe Blain
2023-01-12  2:51 ` Teng Long [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=20230112025137.4286-1-tenglong.tl@alibaba-inc.com \
    --to=dyroneteng@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=sunshine@sunshineco.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.