git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Linus Arver <linusa@google.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2023, #05; Fri, 15)
Date: Tue, 19 Sep 2023 13:00:38 -0700	[thread overview]
Message-ID: <owly7comj5ll.fsf@fine.c.googlers.com> (raw)
In-Reply-To: <xmqqmsxmdhdw.fsf@gitster.g>

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

> [Cooking]
>
> [...]
>
> * la/trailer-cleanups (2023-09-11) 6 commits
>   (merged to 'next' on 2023-09-12 at 779c4a097a)
>  + trailer: use offsets for trailer_start/trailer_end
>  + trailer: rename *_DEFAULT enums to *_UNSPECIFIED
>  + trailer: teach find_patch_start about --no-divider
>  + trailer: split process_command_line_args into separate functions
>  + trailer: split process_input_file into separate pieces
>  + trailer: separate public from internal portion of trailer_iterator
>
>  Code clean-up.
>
>  Will merge to 'master'.
>  source: <pull.1563.v2.git.1694240177.gitgitgadget@gmail.com>

This isn't ready yet (still need to reroll).

> [...]
>
> * la/trailer-test-and-doc-updates (2023-09-07) 13 commits
>  - trailer doc: <token> is a <key> or <keyAlias>, not both
>  - trailer doc: separator within key suppresses default separator
>  - trailer doc: emphasize the effect of configuration variables
>  - trailer --unfold help: prefer "reformat" over "join"
>  - trailer --parse docs: add explanation for its usefulness
>  - trailer --only-input: prefer "configuration variables" over "rules"
>  - trailer --parse help: expose aliased options
>  - trailer --no-divider help: describe usual "---" meaning
>  - trailer: trailer location is a place, not an action
>  - trailer doc: narrow down scope of --where and related flags
>  - trailer: add tests to check defaulting behavior with --no-* flags
>  - trailer test description: this tests --where=after, not --where=before
>  - trailer tests: make test cases self-contained
>
>  Test coverage for trailers has been improved.
>  source: <pull.1564.v3.git.1694125209.gitgitgadget@gmail.com>

Did you forget to add "Need more reviews"? Not sure what the status is
for the overall series (modulo your targetd comments for some of the
patches).

  parent reply	other threads:[~2023-09-19 20:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-16  1:41 What's cooking in git.git (Sep 2023, #05; Fri, 15) Junio C Hamano
2023-09-19 18:32 ` Taylor Blau
2023-09-24 19:59   ` SZEDER Gábor
2023-09-25 23:06     ` Taylor Blau
2023-09-19 20:00 ` Linus Arver [this message]
2023-09-19 20:16   ` Junio C Hamano
2023-09-19 21:25   ` Junio C Hamano
2023-09-20  6:37     ` Linus Arver
2023-09-20 14:57       ` Junio C Hamano
2023-09-20 19:20         ` Linus Arver

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=owly7comj5ll.fsf@fine.c.googlers.com \
    --to=linusa@google.com \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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).