git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Emily Shaffer <emilyshaffer@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2020, #06; Mon, 24)
Date: Tue, 25 Aug 2020 12:42:09 -0700	[thread overview]
Message-ID: <20200825194209.GB331156@google.com> (raw)
In-Reply-To: <xmqq7dtn3785.fsf@gitster.c.googlers.com>

> * es/config-hooks (2020-07-30) 6 commits
>  - hook: add 'run' subcommand
>  - parse-options: parse into argv_array
>  - hook: add --porcelain to list command
>  - hook: add list command
>  - hook: scaffolding for git-hook subcommand
>  - doc: propose hooks managed by the config
> 
>  The "hooks defined in config" topic.
> 
>  Expecting a reroll.
>  Now jk/strvec is in 'master', we may want to see the topic reworked
>  on top of it.  Are there unresolved issues, or does the topic need
>  a round of detailed review?

I have it reworked locally to use strvec instead. I see in
https://lore.kernel.org/git/xmqqsgd8606c.fsf@gitster.c.googlers.com that
you were waiting for another jk/strvec reroll and it looks like that's
happened now, so I'll rebase this series against 'master' once more.

I'm ready for the first four (five?) of the series to receive a detailed
review, but I think it's premature for the 6th to be considered before
I've seen what the conversion process looks like for existing hook
callers. That's my main focus right now, although it tends to be bumped
by concerns for the summit next month as well as pesky life events.

 - Emily

      parent reply	other threads:[~2020-08-25 19:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-25  0:22 What's cooking in git.git (Aug 2020, #06; Mon, 24) Junio C Hamano
2020-08-25  8:58 ` pw/add-p-allowed-options-fix, was " Johannes Schindelin
2020-08-25 15:46   ` Junio C Hamano
2020-08-25 19:42 ` Emily Shaffer [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

  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=20200825194209.GB331156@google.com \
    --to=emilyshaffer@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).