From: Emily Shaffer <emilyshaffer@google.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: es/config-hooks, was Re: What's cooking in git.git (Jul 2020, #02; Thu, 9)
Date: Wed, 15 Jul 2020 16:13:11 -0700 [thread overview]
Message-ID: <20200715231311.GJ3189386@google.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2007152247210.52@tvgsbejvaqbjf.bet>
On Wed, Jul 15, 2020 at 10:50:49PM +0200, Johannes Schindelin wrote:
> cc: git@vger.kernel.org, Emily Shaffer <emilyshaffer@google.com>
>
> Hi Junio & Emily,
>
> On Thu, 9 Jul 2020, Junio C Hamano wrote:
>
> > * es/config-hooks (2020-05-21) 4 commits
> > - 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.
> >
> > What's the status of this one? Abandoned?
>
> This patch series is unfortunately still breaking on Windows, at least in
> the version carried in `seen`. It _still_ needs the patch I provided in
> https://lore.kernel.org/git/nycvar.QRO.7.76.6.2005250055180.56@tvgsbejvaqbjf.bet/
> and the patch (which I accidentally reversed) that I provided in
> https://lore.kernel.org/git/nycvar.QRO.7.76.6.2005250053080.56@tvgsbejvaqbjf.bet/
I haven't had time to work on it until this week (I am working on it
now). I think I have these patches applied locally, or if not I will
make sure to apply them before I send another round. Probably I can send
that end of the week. I don't think there have been any new rounds of it
since you send those two patches, right? Sorry for the inconvenience.
- Emily
prev parent reply other threads:[~2020-07-15 23:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 21:40 What's cooking in git.git (Jul 2020, #02; Thu, 9) Junio C Hamano
2020-07-10 2:26 ` Taylor Blau
2020-07-15 20:50 ` es/config-hooks, was " Johannes Schindelin
2020-07-15 23:13 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200715231311.GJ3189386@google.com \
--to=emilyshaffer@google.com \
--cc=Johannes.Schindelin@gmx.de \
--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 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.